Device-driven intelligence and feedback for performance optimization and planning of a service network

ABSTRACT

System(s), device(s), method(s), and user interfaces are provided to enable a subscriber device to report network operation conditions, such as network performance incidents, to receive feedback from the network related to the incident and available or possibly available solutions, and to produce network intelligence suitable for network planning and network performance enhancement. Reporting of network performance incidents can be characterized by location and time of occurrence, wherein these intelligence is provided by the user device. Feedback provided by the network is based on the network performance data received as part of reporting an incident. The reporting described herein enables a network operator to generate network planning intelligence based on actual network performance as experienced at the subscriber level.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, moreparticularly, to enabling a user device to supply network operation databased on specific network performance conditions, and to allow a networkthat serves the user device to deliver feedback associated with thesupplied network operation data and to plan network deployment and toenhance network performance.

BACKGROUND

Service and related customer support significantly affect subscriberattrition. Conventionally, wireless service providers provide variousconduits for a subscriber to request support and to report networkoperation incidents. Subscriber reported problems related to networkperformance are a vital source of feedback to a network operator, orservice provider, as certain subscriber reported problems are visibleonly to the subscriber, such as when the subscriber attempts to utilizea user mobile device in an area where the network operator does notprovides coverage. Such scenario can arise, for example, in areas inwhich the network operator has a license to a portion of electromagneticradiation spectrum, but does not provide indoor coverage to a specificbuilding deployed in an operating area for the license.

Nevertheless, regardless of the various conduits, quality of theresponse of the service provider to a network performance incident isdictated primarily by a limited number of resources generally availablefor support services in the network; the number of resources is directlyrelated to the number of employees the wireless service provider has instaff or has contracted. In addition, in conventional systems,resolution of network performance incidents that are submitted via thevarious typical conduits available to a subscriber involves recreatingthe network performance incident by dispatching technician(s) to alocation at which the incident has occurred. Accordingly, customerservice becomes costly and is based on rather limited input with respectto information necessary for expeditious and robust resolution ofnetwork operation issue(s) that caused the network performanceincidents.

SUMMARY

The following presents a simplified summary of the disclosure in orderto provide a basic understanding of some aspects thereof. The subjectsummary is not an extensive overview of the disclosure. It is intendedto neither identify key or critical elements of the disclosure nordelineate any scope. The sole purpose of the subject summary is topresent some concepts of the subject disclosure in a simplified form asa prelude to the more detailed description that is presented later.

The subject disclosure provides system(s), device(s), and method(s) toenable a subscriber device to report network operation conditions, suchas network performance incidents, and to receive feedback from thenetwork related to the incident and available or possibly availablesolutions. Reporting of network performance incidents can becharacterized by location and time of occurrence, wherein thisintelligence is provided by the user device. Feedback provided by thenetwork is based on the network performance data received as part ofreporting an incident. The reporting described herein enables a networkoperator to generate intelligence for network planning and for networkperformance improvement or optimization based on actual networkperformance as experienced at the subscriber level. Thus, allocation ofresources for network optimization and development is based on objectivedata rather than mainly on simulations or management subjective input orperspective.

One of the various advantages of the subject disclosure is that pushing,or shifting, collection of network performance data to subscribers of anetwork operator allows the network operator to access networkperformance more broadly and with higher detail than throughconventional approaches. Since the subscribers that report an incidentare experiencing the network issue, the subscribers can report thespecifics of time, location, details of incident, related events, andenvironment of the incident that are difficult if not impossible toreproduce by a network engineer dispatched to the location to respond tothe reported network performance incident.

Aspects, features, or advantages of the subject innovation can beexploited in substantially any wireless telecommunication, or radio,technology; for example, Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMAX); Enhanced General Packet Radio Service (Enhanced GPRS);Third Generation Partnership Project (3GPP) Long Term Evolution (LTE);Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband(UMB); 3GPP Universal Mobile Telecommunication System (UMTS); High SpeedPacket Access (HSPA); High Speed Downlink Packet Access (HSDPA); HighSpeed Uplink Packet Access (HSUPA), or LTE Advanced. Additionally,substantially all aspects of the subject disclosure can include legacytelecommunication technologies.

It is noted that while various aspects, features, or advantages of thesubject innovation are illustrated through Wi-Fi access point(s) andassociated Wi-Fi coverage, such aspects and features also can beexploited in confined-coverage base stations (e.g., home-based accesspoint(s), enterprise-based access point(s)) that provide wirelesscoverage through most any, or any, disparate telecommunicationtechnologies such as for example femtocell telecommunication or picocelltelecommunication.

To the accomplishment of the foregoing and related ends, the subjectdisclosure, then, comprises the features hereinafter fully described.The following description and the annexed drawings set forth in detailcertain illustrative aspects of the subject disclosure. However, theseaspects are indicative of but a few of the various ways in which theprinciples of the disclosure may be employed. Other aspects, advantagesand novel features of the disclosure will become apparent from thefollowing detailed description when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A illustrates a block diagram of an example system that can enableand exploits various aspects described herein. FIG. 1B is an exampleembodiment of a feedback component that is part of the example systemdepicted in FIG. 1A.

FIG. 2 describes an example embodiment of a device that can reportnetwork performance incidents and receive related feedback in accordancewith aspects described herein.

FIGS. 3A-13C present various example user interfaces that allow adevice, wireless or otherwise, to enable various aspects of the subjectdisclosure.

FIG. 14A is a block diagram of an example system that can generate anddeliver network feedback based at least on received network performancedata in accordance with aspects of the subject disclosure. FIG. 14Billustrates an example network intelligence based on the receivednetwork performance data in accordance with an aspect described herein.

FIG. 15 is a block diagram of an example network environment that canenable various aspects of utilization of reports of network performanceincident and related data in accordance with aspects of the subjectdisclosure.

FIG. 16 displays a flowchart of an example method for reporting anetwork performance incident in accordance with one or more aspectsdescribed herein.

FIG. 17 presents a flowchart of an example method for deliveringinformation that characterizes a network performance incident andrelated data according to aspects of the subject disclosure.

FIG. 18 presents a flowchart of an example method for supplying end-usersupport content according to aspects of the subject disclosure.

FIG. 19 is a flowchart of an example method for acquiring competitivedata on network performance in accordance with aspects described herein.

FIG. 20 is a flowchart of an example method for acquiring information onnetwork performance in accordance with an aspect disclosed herein.

FIG. 21 is a flowchart of an example method for acquiring feedback onnetwork operation and related performance incidents according to aspectsdescribed herein.

FIG. 22 presents a call flow of an example method for establishinginteractive feedback delivery according to aspects of the subjectdisclosure.

FIG. 23 is a flowchart of an example method for producing networkintelligence based at least on data received through report(s) of one ormore network performance incidents according to aspects of the subjectdisclosure.

FIG. 24 is a flowchart of an example method for supplying data to adevice that can report a network performance incident in accordance withaspects described herein.

FIGS. 25-26 is an example system that enables various aspects ofdevice-driven intelligence and feedback for performance enhancement andplanning of a service network described herein.

DETAILED DESCRIPTION

Several aspects of the subject disclosure are now described withreference to the drawings, wherein like reference numerals are employedto refer to like elements throughout. In the following detaileddescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of the presentdisclosure. It may be evident, however, that the present invention maybe practiced without these specific details. In other instances,well-known structures and devices are shown in block diagram form inorder to facilitate describing the present invention.

As used in this application, the terms “component,” “system,”“platform,” “interface,” “node,” “layer,” “tier” and the like areintended to refer to a computer-related entity or an entity related toan operational apparatus with one or more specific functionalities,wherein the entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentcan be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a server and the server can be a component. One or more componentsmay reside within a process and/or thread of execution and a componentmay be localized on one computer and/or distributed between two or morecomputers. In addition, these components can execute from variouscomputer readable media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry which is operated by asoftware application or a firmware application executed by a processor,wherein the processor can be internal or external to the apparatus andexecutes at least a part of the software or firmware application. As yetanother example, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can include a processor therein to executesoftware or firmware that confers at least in part the functionality ofthe electronic components. As still yet another example, interface(s)can include input/output (I/O) components as well as associatedprocessor, application, or Application Programming Interface (API)components. While the foregoing examples are directed to illustrativeaspects of a component, the illustrated aspects or features also applyto a system, platform, interface, node, layer, and the like.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point;” “base station,”“Node B;” “evolved Node B (eNode B);” “home Node B (HNB)” or “homeaccess point (HAP),” which include femtocell access point, picocellaccess point, Wi-Fi base station, etc.; and the like, are utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or apparatus that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Sources orrecipients of such data, control, voice, video, sound, gaming, orsubstantially any or any data stream or signaling stream can be at leasta set of network components such as, but not limited to, user equipment,customer premises equipment, network servers, controllers, gateways ormanagement components. Data and signaling streams can be packetized orframe-based flows. It is noted that context in the subject specificationgenerally distinguishes among a base station that provides or isintended to provide primarily outdoor wireless coverage and a and afacility-based (e.g., home) access point (e.g., femtocell AP) thatprovides or is intended to provide primarily indoor wireless coveragewithin a confined range. Explicit distinction between indoor-serving APand outdoor-serving base station is made when context may beinsufficient to distinguish the utilized terms.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. As utilized herein, the term “prosumer”indicate the following contractions: professional-consumer andproducer-consumer.

Features or aspects described in the subject disclosure can rely, atleast in part, on delivery or reception of directive(s), indication(s),request(s), or the like, and information or payload data (e.g.,content(s)) associated therewith. Directive(s) can be embodied inmulti-bit words (e.g., P-bit words, with P a positive integer) and codedto specifically convey a request to a particular functional element(e.g., a mobile device, a femtocell AP, a network node) in order toexecute one or more specific operation. Information or payload datawithin signaling, and request(s) or indication(s) conveyed therein, canbe embodied, for example, in one or more reserved bits in a packetheader, a light-payload (e.g., of the order of 1 byte) data packet, apredetermined multi-bit word conveyed in a control channel, alightweight file (e.g., a cookie), an email communication, an instantmessage, or the like. In addition, directive(s), request(s),indication(s), or the like, as described herein, can be delivered inaccordance with various communication protocols. As an example, thevarious protocols can include at least one of file transfer protocol(FTP), secure shell FTP (SFTP), FTP over secure socket layer (FTPS),short message service (SMS) protocol, multimedia messaging service (MMS)protocol, unstructured supplementary service data (USSD) standard,simple network management protocol (SNMP), lightweight directory accessprotocol (LDAP), session initiation protocol (SIP), SIP for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Open MobileAlliance (OMA) device management (DM) protocol, Technical Report 069(TR-069) protocol, also referred to as Customer Premise Equipment (CPE)Wide Area Network (WAN) Management Protocol or CWMP, or the like.

The term “intelligence” as utilized herein with respect to a networkrefers to substantially any, or any, information that characterizes awireless network or non-mobile network such for example, coveragearea(s), operation marketplace(s), subscriber information, serviceofferings and associated promotional and advertising campaigns,commercial (e.g., sales, earnings, operational margins, costs) andnon-commercial (community outreach, philanthropy . . . ) activitiesinvolving offered services or products, or the like. In connection withterminology employed to identify networks, mobile or otherwise, an“owned network,” or the like, refers to the network that manages one ormore components that perform the various functionalities described inthe subject specification, a “competing network,” “non-owned network,”or the like, refers to one or more networks that share a market with theowned network.

Referring to the drawings, FIG. 1A illustrates an example system 100that enables and exploits reporting of network performance incidents inaccordance with aspects described herein. In the subject example system,a set of one or more device(s) 104 can report or provide at least onenetwork performance incident, or “network problem”, to a networkplatform 120 operated by a service operator. The at least one networkperformance incident is specific to the service provided by the network.In a telecommunication network, the at least one network performanceincident can be at least one of a dropped or lost call, no coverage,voice quality issues, etc. In a wireline network, such as a digitalcable service, the at least one network performance incident can includepoor image quality, unavailability of programming guide, authenticationfail instance(s) for pay-per-view programming, or the like. The set ofone or more device(s) 104 includes at least one of a mobile device or awireline device (e.g., customer premise equipment, such as DVR,femtocell access point, Wi-Fi access point, digital television, or thelike). A mobile device can be user equipment or any device enabled forwireless communication, such as a cellular telephone; a portablecomputer (e.g., netbooks or laptops); personal digital assistants(PDAs); a Moving Picture Experts Group (MPEG)-1 Audio Layer 3 (MP3)player; a portable radio tuner (satellite-signal based or conventional);a portable gaming box; or the like. A wireline device can be one of awireline telephone, a tethered personal computer, a set top box, atelevision (TV) set, a stereo music player, a tethered radio tuner, atethered gaming box (e.g., set top box), a digital video recorder (DVR),or the like.

Reporting of a network performance incident can be accomplished throughdelivery of a report 110 that includes information that specifies thenetwork performance incident, also referred to as incident, and at leastone of a location (R) associated with the incident and a time stamp (c)assigned to the incident. An incident report component 106 functionallycoupled to a display interface 108 enable, at least in part, generationand delivery of report 110. Incident report component 106 can receivedata from display interface 108 to specify, at least in part, thereport. In an aspect, display interface can render various userinterfaces that enable collection of input data from an operator of thedevice that includes incident report component 106, and generates report110. In addition, in an aspect of the subject disclosure, incidentreport component can acquire (e.g., receive or retrieve) request(s) fordata from display interface 108, where the incident report component 106delivers such request(s) to feedback system 140 to retrieve, orotherwise access the requested data; display interface 108 can rendervarious user interfaces that enable generating such request(s) andconveying the request(s) to incident network component 106. Moreover, inanother aspect, incident network component 106 can generate and deliverrequests for data associated with network service(s) (e.g.,location-based service, alerting services . . . ) to feedback system140, and convey data so acquired to display interface 108. Furthermore,in yet other aspects, incident report component 106 can receiveinstructions to effect specific actions, such as conduct a diagnosticcycle test, or scan a wireless environment in the neighborhood of thedevice that includes incident report component 106. After completion ofsuch actions, incident report component 106 can deliver the datacollected in response to the received instruction to feedback system140. Several of such aspects will be described in greater detailhereinafter.

In an aspect, the location conveys at least two coordinates (e.g.,latitude, longitude), which can be generated at the device, via incidentreport component 106, through data originated in global navigationsatellite system (GNNS), such as global positioning system (GPS),assisted global positioning system (AGPS), Galileo, or GLONNAS(Global'naya Navigatsionnaya Sputnikovaya Sistema or Global NavigationSatellite System), or data acquired from network platform 120 or anetwork node that provides location-based services and is functionallycoupled to network platform 120. In addition, in certain embodiments, Ralso can convey one or more of altitude, course, horizontal accuracy orvertical accuracy. The report 110, and associated payload, is deliveredto the network platform 120 through access network(s) 114, which can bespecific to the service for which the network performance incident isreported. In an aspect, the report 110 is delivered as a data messagegenerated by incident report component 106; however, other messagingcommunications, such as SMS or MMS, also can deliver report 110. Formacro-cellular wireless service, access network(s) 114 include a radioaccess network (RAN) that enables delivery of report 110, whereas forfemtocell wireless service, access network(s) 152 can include at leastone DSL access multiplexer (DSLAM) and at least one broadband remoteaccess server (B-RAS).

In response to receiving report 110, network platform 120 providesfeedback data 150, also referred to as feedback 150. The delivery offeedback 150 can be automatic (e.g., without human intervention). To atleast that end, network platform 120 supplies the report 110, andrelated information, to feedback system 140, which produces feedback150. In an aspect, gateway (gty) node(s) 124 can acquire (e.g., receiveor retrieve) the report 110 and convey it to middleware component 130,which can relay the report 110 to feedback system 140. Middlewarecomponent 130 allows functional coupling to and utilization of systemsexternal to network platform or legacy systems.

Feedback system 140 can process network operation data conveyed inreports from various devices and related locations and time stamps, andgenerate feedback information (e.g., feedback data 150) suitable for adevice reporting a network performance incident. In an aspect, analysiscomponent 144 can correlate all or substantially all available datarelated to network performance incidents from a plurality of customersin a specific area (e.g., metropolitan market) and can access disparatenetwork systems to establish if the reported network performanceincident is “new” or recurring. As an example, the network systems cancomprise operation layer(s) 160 or external layer(s) 170. Operationlayer(s) 170 can include one or more of operation and maintenance (O&M)layers, network-planning layer(s), marketing layer(s), businesslayer(s), whereas external layer(s) 170 can include vendor layer(s),contractor layer(s), regulation layer(s), or the like. For example,regulation layer(s) can indicate when additional spectrum is availablefor purchase or free-of-charge utilization. Based on the correlationassessment, analysis component 144 can associate available networkplanning information to one or more categories of network performanceincidents and convey such association to feedback component 148, whichcan provide (e.g., generate and deliver) feedback data 150. As anexample, the one or more categories can include lost or dropped callsession; failed call session attempt; absence of coverage; data failure;poor voice quality (e.g., excessive jitter or noise interference); orthe like. Feedback data 150 can be received by gateway node(s) 124 innetwork platform 120, and the gateway node(s) 124 can relay the feedbackdata 150 to the device that delivered network performance incidentreport 110.

In an aspect of the subject disclosure, feedback 150 can be delivered toa device in a form of network news in response to delivery of report 110via, at least in part, incident report component 106. Accordingly, everysubmission of report 110 can have a “feedback response” from the networkoperator. Feedback system 140 can deliver the feedback response(feedback 150) through various messaging mechanisms. In an aspect, thefeedback response can be a short message service (SMS) communication ora multimedia messaging service (MMS) communication. In another aspect,the feedback response can be a data message incorporated in the incidentreport component 106 in the device utilized to report the networkperformance incident. In an embodiment, the incident report component106 can be a software or firmware application retained as one or moresets of code instructions in a memory within the device utilized toreport the network performance incident or in a memory functionallycoupled to such device. In such embodiment, feedback system 140 canconvey the feedback response (e.g., feedback 150) to the device, whichcan render the data message as part of execution of the software orfirmware application that embodies the incident report component 106.

Feedback 150 can include a message (SMS, MMS, or other data message)that acknowledges reception of report 110. In addition or in thealternative, feedback 150 can supply, through various messagingmechanisms, specific information related to existing network developmentplans, which can be accessed by feedback component 148 through memory152 or via operation layer(s) 160 or external layer(s) 170. Content ofthe information can be tailored to a subscriber in response toadditional data included as part of report 110 or data supplied as partof a subscriber feedback mechanism enabled through incident reportcomponent 106. In an embodiment, such messaging can be providedinitially free-of-charge to subscriber the own or lease a device thatincludes incident report component 106. Analysis component 144 can trackperceived benefit of allowing messaging for those subscribers and basedon assessment of the perceived benefit, a network operator that providesservice to device(s) 104, can incentivize those subscribers to purchasea recurring network messaging service.

In an embodiment, e.g., 180 illustrated in FIG. 1B, a report component182 in feedback component 148 can deliver feedback 150. In an aspect,report component 182 can format the payload data in feedback 150 and canformat data that is received as part of network performance incidentreport 110. In alternative or additional embodiments, feedback component148 also can include an interactive feedback component (not shown) thatcan provision, at least in part, an interface to receive, or exchange,feedback interactively amongst a device in the set of one or moredevices 104 and feedback system 140.

As indicated supra, information in messages can respond to simpleinquiries posed by a subscriber through a device that includes incidentreport component 106. However, feedback system 140 can provide afeedback response through messaging without receiving an inquiry fromthe device. For example, for network development plans that includedeployment of a base station within a predetermined period (e.g., 60days), feedback component 148 can deliver a SMS communication or MMScommunication to a group of devices that have reported incidents in thearea in which the base station is planned to be deployed. Feedbacksystem 140, via analysis component 144, can determine the area toexamine for submitted reports based at least on a circle with radiusequal or nearly equal to the minimum of (a) the distance to aneighboring base station or the maximum or (b) the maximum typicaldistance of intended coverage of the base station for a particularmorphology. Analysis component 144 can process data on previouslysubmitted reports, e.g., analysis component 144 can filter out duplicateproblems per customer. In addition, analysis component 144 can reviewreports submitted within a predetermined period of time, e.g., 60 days.In an aspect, the group of devices that receive a message shouldcontinue to experience difficulties at the time of message delivery, toincrease perceived benefit of messaging.

In embodiment 180, query component 184 can manage (receive, format,convey, etc.) any or most any received inquiry from a device or from anetwork node element, which can be part of operation layer(s) 160, orexternal layer(s) 170. Subscription manager component 186, also referredto as subscription manager 186, can administer, e.g., create, update,suspend, terminate, subscription related to feedback 150, particularly,though not exclusively, in connection with network news or alerts.

Feedback system 140 can provide feedback 150 in accordance at least inpart with the network performance incident that is reported. In anaspect, for an incident related to a “problem noted in a certain area”where the problem is associated with a cell site with an operationissue, the feedback in the form of “news,” for example, can be renderedas an alert in the device that delivers the report (e.g., report 110)for the incident and that includes incident report component 106. Forinstance, the alert can include a message that discloses informationthat characterizes a course of action aimed to resolution of issuesrelated to the network performance incident that is reported; as anillustration, the message can be “technical difficulties have been notedin the area, and a solution is expected within the next 24 hs”. Inanother aspect, for network performance incidents reported in an areaand related to capacity, feedback system 140 can search for available“capacity augmentation plans” in a database of the service provider;feedback system 140 exploits one or more plans so identified andprovides (e.g., issues and delivers) network news as to when capacityadditions will be deployed. If the problem reported in an area isrelated to coverage, and the network operator has coverage improvementplans, then feedback related to the coverage improvement plans can beprovided. If the problem reported is related to performance that is notcoverage or capacity, and the network operator has performanceimprovement plans in place, the subject disclosure enables the networkoperator to convey those plans and ETA via at least network news. If theproblem lacks specific known plans for development(s) that can resolvethe problem, then the network operator has the ability to create aticket, and can inform the customer that a ticket has been created andsupply related ticket information; in an aspect, the network operatorcan created the ticket, or service ticket, via, for example, feedbacksystem 140.

In another aspect of the subject innovation, feedback 150 can besupplied to a device within the set of device(s) 106 as part of analerting service, to which the device can subscribe. The alertingservice can provide network development information related to specificarea(s); such information can include planned deployments of basestations, addition Subscription to the alerting service can be allowedat a time the device delivers an initial network performance incidentreport or at a time the device deploys, e.g., installs, builds, andactivates, the incident report component 106. To deliver information orcontent as part of the alerting service, in one embodiment, server(s)156 can include at least one application server that can extract networkalerts or news from a memory or memory element (e.g., a database) inresponse to a query from a device that subscribes to the alertingservice. The query can be received and processed by the at least oneapplication server in server(s) 156. In the alternative, a databasemanager component (not shown), which can be part of feedback component148 can receive and process the query. A server or node that is part ofoperation layer(s) 160, e.g., network and marketing layer, can providecontent to the memory or the memory element.

Server(s) 156 can include at least one or more processors (not shown)configured to enable or that enable, at least in part, the functionalityof feedback system 140, and components therein. To that end, at leastthe one or more processors can execute one or more sets of codeinstructions (not shown) stored in memory 152 (or othercomputer-readable storage medium), for example. In an aspect, the one ormore set of code instructions, when executed by the at least one or moreprocessors (not shown) in server(s) 156 can carry out one or more of theexample methods disclosed herein; such code instructions provide acomputer-executable or machine-executable framework to enact suchexample methods and enable at least a portion of the functionality offeedback system 140 described herein. Server(s) also can include aninput/output (I/O) interface that enables communication with an externalnetworked apparatus (a device, a server, a memory, etc.). Server(s) 156can exchange data and signaling, code instructions, directives, andforth, with one or more of analysis component 144, feedback component148, or memory 152 via bus 157. In addition, analysis component 144,feedback component 148, memory 152, or any combination thereof, also canexchange data and signaling, code instructions, directives, etc. throughbus 157. In an aspect, bus 157 can be embodied in one or more of asystem bus, an address bus, a message bus, a memory bus, a power bus inaccordance with various hardware, firmware, or software implementations.

FIG. 2 is an example embodiment 200 of a device that enables andexploits various aspects of the subject disclosure. Device 202 can be amobile device or a wireline device (e.g., a pseudo-stationary ortethered device) that can communicate wirelessly. Device 202 can embodyany device that can report a network performance incident through anincident report component (e.g., 106) in accordance with aspectsdescribed herein. As an example, collection component 232, locationcomponent 267, and scanner component 225 can embody such incident reportcomponent. As described supra, in an aspect, collection component 232,location component 267, and scanner component 225 can be retained inmemory 285 as one or more sets of code instructions; in such scenario,the incident report component (e.g., 106) is embodied in a softwareapplication or firmware application that, when executed by processor(s)275, provides the functionality described herein. In example, embodiment200, display interface 245 can embody display interface 245, which canacquire input and provide such input as data or signaling to one or morecomponents of device 202.

To enable wireless communication, and transmit and receive data andsignaling wirelessly, device 202 includes a communication platform 204,which comprises a set of receiver(s)/transmitter(s) 206; eachtransceiver in the set includes an antenna 215 _(λ), with λ=1, 2, . . .K, where K is a natural number greater or equal than unity. One or moreof receiver(s)/transmitter(s) 206 can be configured, e.g., by a basestation or component(s) therein, to operate in various telecommunicationmodes: multiple-input multiple-output (MIMO) mode, multiple-inputsingle-output (MISO) mode, single-input single-output (SIMO) mode, orsingle-input single-output (SISO) mode. Receiver(s)/transmitter(s) 206include respective filter(s) and amplifiers. The filters are installedbetween antenna(s) 215 _(λ), and the amplifier(s), and tune specificportions of electromagnetic (EM) radiation spectrum available fortelecommunications.

Communication platform 204 comprises electronic components andassociated circuitry that enable processing and manipulation, e.g.,coding/decoding, deciphering, modulation/demodulation, of wirelesssignal(s) received by device 202 and wireless signal(s) to betransmitted by device 202; the wireless signal(s) modulated and coded,or otherwise processed, in accordance with various radio technologyprotocols. Components, or functional elements, in communication platform204 exchange information through a bus 214; information includes data,code instructions, signaling, or the like, and the bus 214 can beembodied in at least one of a system bus, and address bus, a data bus, amessage bus, or a reference link or interface. The electronic componentsand circuitry can include the set of K receiver(s)/transmitter(s) 206and component(s) therein, a multiplexer/demultiplexer (mux/demux)component 207, a modulator/demodulator component 209, a coder/decoder211, and a set of one or more chipsets, e.g., multi-mode chipset(s) 213.As indicated above, the transceivers includes receiver(s)/transmitter(s)206 that can convert signal from analog to digital upon reception, andfrom digital to analog upon transmission. Receiver(s)/transmitter(s) 206also can divide a single data stream into multiple parallel datastreams, or perform the reciprocal operation; such operations typicallyconducted in various multiplexing schemes. Functionally coupled toreceiver(s)/transmitter(s) 206 is a multiplexer/demultiplexer(mux/demux) component 207 that enables processing or manipulation ofwireless signal(s) in time and frequency space or domain. Electronicmux/demux component 207 can multiplex and demultiplex information(data/traffic and control/signaling) according to various multiplexingschemes such as time division multiplexing (TDM), frequency divisionmultiplexing (FDM), orthogonal frequency division multiplexing (OFDM),code division multiplexing (CDM), space division multiplexing (SDM). Inaddition, mux/demux component 207 can scramble and spread information(e.g., codes) according to substantially any code; e.g., Hadamard-Walshcodes, Baker codes, Kasami codes, polyphase codes, and so on. Amodulator/demodulator (mod/demod) component 209 also is a part ofcommunication platform 204, and can modulate and demodulate informationaccording to various modulation techniques, such as frequency modulation(e.g., frequency-shift keying), amplitude modulation (e.g., M-aryquadrature amplitude modulation (QAM), with M a positive integer;amplitude-shift keying (ASK)), phase-shift keying (PSK), and the like.In embodiment 200, mod/demod component 209 is functionally coupled tomux/demux component 207 via bus 214. In addition, processor(s) 275enables, at least in part, device 202 to process data (e.g., symbols,bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as implementing direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc.

Communication platform 204 also includes a coder/decoder 211 thatoperates on data in accordance with one or more coding/decoding schemessuitable for telecommunication through one or morereceivers(s)/transmitter(s) 204. When communication platform 204exploits MIMO, MISO, SIMO modes of operation, coder/decoder 211 canimplement at least one of space-time block coding (STBC) and associateddecoding; or space-frequency block (SFBC) coding and associateddecoding. Coder/decoder 211 also can extract information from datastreams coding in accordance with spatial multiplexing scheme. To decodereceived information, e.g., data or control signaling, coder/decoder 211can effect at least one of computation of log-likelihood ratios (LLR)associated with constellation realization for a specific demodulation;maximal ratio combining (MRC) filtering, maximum-likelihood (ML)detection, successive interference cancellation (SIC) detection, zeroforcing (ZF) and minimum mean square error estimation (MMSE) detection,or the like. In addition, to operate in the manner described herein,coder/decoder 211 can employ, at least in part, mux/demux component 207and mod/demod component 209.

A network operator can configure, as part of provisioning of device 202,a set of electromagnetic (EM) radiation frequency bands and a set ofradio technologies that communication platform 204 and componentstherein can exploit for wireless communication. The set of EM radiationfrequency bands, also referred to herein as frequency bands, cancomprise radio frequency (RF) portion(s) and microwave portion(s) of theEM spectrum, although other spectral regions such as infrared (IR) alsocan be included. In an aspect, the set of EM radiation frequency bandscan include at least one of (i) all or substantially all EM frequencybands licensed by the network operator (e.g., PCS bands, AWS bands, GWCSbands, and so forth); or (ii) all or substantially all unlicensedfrequency bands currently available for telecommunication (e.g., the 2.4GHz Industrial, Scientific and Medical (ISM) band or one or more of theUnlicensed National Information Infra-structure (UNII) bands in the 5GHz range). It is noted that as part of network upgrades, the networkoperator can add frequency bands, or frequency carriers therein, to theset of EM radiation frequency bands as such bands or carriers becomeavailable for telecommunication, e.g., auctioned for utilization orauthorized for free-of-charge utilization. Similarly, as new radiotechnologies become standardized, or available, the network operator canintroduce such technologies in the set of radio technologies that can beutilized for telecommunication by device 202.

Additionally, in embodiment 200, multimode chipset(s) 213 can allowdevice 202 to operate in multiple communication modes through variousradio network technologies (e.g., second generation (2G), thirdgeneration (3G), fourth generation (4G)) or deep-space satellite-basedcommunication in accordance with disparate technical specifications, orstandard protocols, for the radio network technologies or satellitecommunication. In an aspect, multimode chipset(s) 213 can enable, atleast in part, communication platform 204 to operate in accordance withstandard protocols specific to a telecommunication mode of operation,e.g., 3GPP Long Term Evolution (LTE)-based communication. In anotheraspect, multimode chipset(s) 213 can be scheduled to operateconcurrently (e.g., when K>1) in various modes or within a multitaskparadigm in which the multimode chipset(s) 213 operates in a dedicatedmode for a specific time interval. In yet another aspect, multi-modechipset(s) enable communication platform 204 to receive globalnavigation satellite system (GNNS) pilot signals (e.g., timingmessage(s), orbit information . . . ) from one or more deployed globalnavigation satellite systems (GNNSs), as indicated supra.

In an aspect, display interface 245 can receive one or more directivesto render an environment (e.g., display one or more user interfaces) toreport a network performance incident, and provide data associatedtherewith, as described supra. In addition, display interface 245 canreceive and process (e.g., decode, encode, format, or deliver) data froma subscriber via one or more gestures (e.g., touch, speech, motion). Inresponse to rendering the environment to report the network performanceincident, the display interface 245 can receive and process data thatspecifies a type of network performance incident or a location of thenetwork performance incident; a data entry interface (not shown), andassociated circuitry, within display interface 245 can manipulate (e.g.,process) a portion of such data (e.g., selection or actuation of asoft-button or other user-device interaction(s)) into data that can beexploited to report the network performance incident. Display interface245 can deliver the data, either raw or processed, to memory 285 to beretained in memory element 293 or data cache 294. Display interface 245also can deliver the data to one or more components within device 202for further processing or delivery to a network platform (e.g., 120).

Further to enabling wireless communication of voice or data, device 202can provide a specific functionality; for instance, device 202 can be amobile phone, a photography camera, a video camera, a wireless dedicatedcomputer (such as a device in an industrial environment), a navigationdevice, a printer or photocopier, a scanner, a fax machine, a televisionset, a digital picture frame, or the like. Such specific functionalitycan be supplied primarily through a functional platform 235 thatcomprises a set of components (not shown) that enable, at least in part,one or more specific functionalities that can complement or supplementwireless communication. It should be appreciated that functionalplatform 235 can exploit an application (either a software applicationor a firmware application) retained in application storage 291 in orderto provide one or more functionalities of device 202; the application isretained as one or more sets of code instructions. As an example, in anaspect of the subject innovation, application storage 291 can include anapplication that, when executed, can provide tutorial(s) for operationof device 202. As another example, when device 202 is a telephone,functional platform 235 can include functional elements such as a dataentry interface (e.g., a touch screen, a keyboard, a biometric pad forbiometric-based access, a microphone, a loud speaker), a camera,peripheral connectors (e.g., a universal serial bus (USB) port or anIEEE 1394 port for transferring data to, or exchanging data with, adisparate device), a voice coder-decoder, which can be part ofcoder/decoder 211; intelligent component(s) that can respond to voiceactivated command(s); and so on.

Device 202 also includes various components that enable functionalityrelated to delivery of network performance reports (e.g., report 110).In an aspect, device 202 can acquire (e.g., receive and detect)satellite-based data through a communication platform 204 and canproduce, via location component 267, a location estimate of a currentlocation of device 202. In addition, device 202 can performtime-of-flight (TOF) measurements via communication platform 204, alocation component 267, and one or more clock layers 236. Timer(s)employed as part of TOF measurements can be enabled by clock layer(s)236. In certain embodiments, clock layer(s) 236 can implement timingprotocols (e.g., Network Time Protocol (NTP)) that enable such timer(s).In one or more embodiments, location component 267 can includecomponents, such as an accelerometer, an altimeter, that can provideadditional positional data for the device; for instance, locationcomponent 267 can provide altitude of the device or heading.

In another aspect, device 202 includes a collection component 232 thatcan acquire (receive, retrieve, etc.) data related with an incidentreport from display interface 245, or data entry interface(s) therein,and supply such data to feedback system 140, via at least in partcommunication platform 204. Collection component 232 also can acquiredata (e.g., from display interface 245) related to requests forservice(s) related to reporting of network performance incidents anddeliver such data to feedback system 140. As example, collectioncomponent can receive from display interface 245 a request forsubscription to a network news or alert service, and deliver the requestto feedback system 140. As another example, collection component canreceive a request for data related to location-based services availableto network platform 120; in particular, though not exclusively, locationcomponent can convey to collection component 232 a request for alocation estimate of ground truth for device 202, and collectioncomponent 232 can relay such request to network platform 120, which canaccess the requested data via feedback system 140 or directly from anetwork node that provides location-based services.

In another aspect, in response to reporting a network performanceincident, scanner component 225 can measure pilot signal(s) within thewireless environment in which device 202 is located and operates. Suchfunctionality is particularly advantageous in cases the networkperformance incident is reported for indoor operation, since currentlyavailable methods to monitor (e.g., measure) indoor radio channelquality or signal strength within building or residences are limited orimpractical. As part of delivery of a network performance report (e.g.,report 110), device 202 can prompt a customer that owns or leases device202 to disclose whether the report is being submitted indoor, outdoor orin transit (e.g., traveling). In response to input data associated withsuch disclosure, collection component 232 can correlate current locationwith location received as part of the input data (e.g., indoor, outdoor,or in transit) and can determine the signal strength indoors. Forexample, signal strength, or radio channel quality, inside the customerhome can be assessed if the location corresponds to the customer's homeaddress which is available to the network operator through billingsystem(s), which can be part of operation layer(s) 160. The datacollected through the scan can be conveyed to the network operator,which can utilize the data to calibrate signal strength indoors for thecustomer that owns or leases the device. In an aspect, scanner component225 conveys the collected data to communication platform 204, which candeliver the collected data to a network platform (e.g., 120) via anaccess network (e.g., 114).

At least one advantage of indoor signal strength assessment as describedhereinbefore is that signal propagation tools that acquire signalstrengths outside of a residence or facility can be calibrated, and thusthe network operator can better model or quantify characteristics ofin-building propagation loss. In addition, the network operator cangenerate or update “per subscriber” model(s) of attrition vulnerabilityoriginated in poor signal quality indoor; in an aspect, analysiscomponent 144 can generate or update such model(s).

Scanner component 225 also can enable “auto-troubleshooting” features.To at least that end, scanner component 225 can monitor operation ofdevice 202 and execute diagnostic cycle(s) (or diagnostic test run(s))that can allow optimization of performance of device 202. In an aspect,execution of the diagnostic cycle(s) conducts one or more data testsdirected to assess, or characterize, one or more of latency (e.g.,roundtrip latency of a data packet) or data rate (or speed). In anotheraspect, such diagnostic cycle(s) can be performed in response tospecific network performance incidents such as data failure. Datacollected as part of the diagnostic cycle(s) can be delivered to thenetwork operator instead of rendered in device 202. For example, peakupload and peak download speeds, or data rates, can be recorded in adiagnostic table database in memory 152. Additionally, in certainembodiments, for a subscriber in a specific segment of subscribers(e.g., employees of network operator), a predetermined code associatedwith the subscriber can be received in the device and, as a result, thedevice validate the predetermined code and, if valid, the device canmodify behavior of or add functionality to diagnostic test run(s)—themodified behavior or added functionality is said to be unlocked by thepredetermined code. Part of the modified behavior or added functionalitycan enable the device 202 to render the results of the diagnostic testrun(s). In an aspect, throughput, speed or data rate, and peak speed orpeak data rate can be rendered, via display interface 245 if device 202receives and validates the predetermined code. In addition, as part ofthe modified behavior or added functionality, scanner component 225 canimplement loop diagnostic test(s) that can probe performance of device202 in cycles until the device 202 receives an indication to terminatethe loop diagnostic test(s). The modified behavior or addedfunctionality remains unlocked during the time interval that device 202renders and environment to report a network performance incident. Afterthe device 202 ceases to render the environment, the modified behavioror added functionality of diagnostic cycles is to be unlocked ifdesired.

In an example scenario related to diagnostic cycle(s), if a customerthat owns or leases device 202 submits a “data problem” on a first radiotechnology (e.g., 3GPP UMTS), scanner component 225 can perform adiagnostic cycle, e.g., an “auto-checking” loop, and detect that asecond radio technology (3GPP LTE, Wi-Fi, femtocell, picocell, etc.) isoperating adequately. Adequate operation can be determined throughcomparison of a key performance indicator (KPI) or performance metricand a related predetermined threshold; KPI or performance metric abovethe predetermined threshold indicates adequate operation. As a result ofthe diagnostic cycle, and identification of second technology asadequate, scanner component 225 can deliver an indication to render amessage that advises a specific action to be performed by the customerthat owns or leases device 202. Display interface 245 can receive theindication and render the message. As an example, the message cansuggest the customer to switch to the second radio technology—inparticular, though not exclusively, the message can suggest consideringconnecting to an open Wi-Fi AP (or hotspots) in proximity of the device202. It should be noted that as part of the diagnostic cycle, scannercomponent 225 can check the at least one Wi-Fi AP for adequate operationprior to issuing such a message. In addition or in the alternative, inresponse to the diagnostic cycle and related findings, scanner component225 can switch to the second radio technology without customerintervention (e.g., automatically); e.g., scanner component 225 cansignal reconfiguration of multimode chipset(s) 213 in order to operatedin the second radio technology that has been identified as operatingadequately.

In the absence of wireless service, a report (e.g., 110) of a networkperformance incident can be queued for delivery after the wirelessservice resumes. In the illustrated embodiment, collection component 232can acquire wireless coverage condition and queue a submission of areport of a network performance incident if the wireless coveragecondition reveals wireless service is unavailable. To acquire wirelesscoverage condition, collection component 232 can poll a memory registerthat contains service status when (e.g., at the time) an indication tosubmit a report is received from display interface 245; the memoryregister can be part of system storage 295 in memory 285. In case thewireless coverage condition indicates that service is unavailable,collection component 232 can continue to poll the memory register,either periodically or according to a predetermined schedule; collectioncomponent 232 delivers the report, via communication platform 204, forexample, if the polling extracts a wireless coverage condition thatreveals wireless service has become available.

Display interface 245 can embody display interface 108 and can rendervisual or aural indicia that control functionality of device 202 assupplied through functional platform 235, or reveal operationalconditions of device 202; for example, battery level, radio technologyemployed for communication, or the like. In addition, display interface245 can render various graphical user interfaces that enable data inputassociated with reporting a network performance incident; in particular,though not exclusively, display interface 245 can render at least theexample user interfaces described in the subject disclosure (e.g., FIGS.3A-13C).

Device 202 includes processor(s) 275 configured to enable or thatenable, at least in part, functionality of substantially any or anycomponent(s) or platform(s), interface(s), and so forth, within device202 in accordance with one or more aspects of the subject disclosure. Inexample embodiment 200, processor(s) 275 is illustrated as external tothe various functional elements (e.g., component(s), interface(s),platform(s)) of device 202; however, in additional or alternativeembodiments, processor(s) 275 can be distributed amongst a plurality ofsuch various functional elements. Processor(s) 275 is functionally(e.g., communicatively) coupled to each functional element within device202 and to memory 285 through bus 295, which can be embodied in at leastone of a memory bus, a system bus, an address bus, a message bus, or oneor more reference link(s) or interface(s). In addition, processor(s) 275can supply information to and retrieve information from memory 285,wherein the information can enable, at least in part, operation and/orcan provide, at least in part, functionality to communication platform205 and at least a portion of component(s) therein; scanner component225; collection component 232; display interface 245; clock layer(s)236; functional platform 235 and component(s) therein; as well as otheroperational components (not shown) of device 202. The information caninclude at least one of code instructions, code structure(s), datastructures, or the like.

Processor(s) 275 can execute code instructions stored in memory 285 toprovide or to enable the described functionality of device 202; the codeinstructions can be retained within application storage 291, systemstorage 295, or other memory(ies) functionally coupled to device 202.Such code instructions can include program modules or softwareapplications or firmware applications that, when executed byprocessor(s) 275, implement various methods described in the subjectdisclosure and that are associated, at least in part, with describedfunctionality of device 202 in connection with supplying a report ofnetwork performance incident(s).

Memory 285 can retain, at least in part in an application storage 291,at least one of data structures (e.g., objects, classes, metadata); codestructure(s) (e.g., modules, procedures) or instructions; orsubstantially any type of software application or firmware applicationthat processor(s) 275 can execute to provide functionality associatedwith substantially any or any component(s), platform(s), interface(s),or functional element(s) within device 202 in accordance with aspects ofthe subject disclosure. In addition, memory 285 can store network ordevice information, e.g., within data storage 293, such as encoded pilotsignal(s); one or more communication protocol(s) or technicalspecification(s); code sequences for scrambling or spreading; blinddecoding hypotheses; semi-persistent scheduling parameters; frequencyoffsets, macrocell and femtocell identifiers (IDs); address book(s); orthe like. Moreover, memory 285 can retain content(s) such as multimediafiles or subscriber-generated data; security credentials (e.g.,passwords, encryption keys, digital certificates, biometric keys such asvoice recordings, iris patterns, fingerprints, deoxyribonucleic acid(DNA) profiles); hardware identifying tokens or codes such as at leastone of an international mobile subscriber identity (IMSI), a temporarymobile subscriber identity (TMSI), packet TMSI (P-TMSI), aninternational mobile equipment identifier (IMEI), an a mobile directorynumber (MDN), a mobile identification number (MIN), a TelecommunicationsIndustry Association (TIA) electronic serial number (ESN), or amulti-bit identification number such as mobile identity number (MEID).It is noted that memory 285 can include affixed or removable elementssuch as a subscriber identification module (SIM) card storage, auniversal integrated circuit card (UICC) storage, or a removable useridentity module (RUIM).

Device 202 also includes power supply 265, which can provide power toone or more components or functional elements that operate within device202. In an aspect, power supply 265 can be rechargeable, e.g., it can beembodied in a rechargeable battery. In addition, power supply 265 caninclude one or more transformers to achieve power level(s) that canoperate device 202 and components or functional elements, and relatedcircuitry therein. In an aspect, power supply 265 can attach to aconventional power grid to recharge, or ensure device 202 isoperational; power supply 265 can include input/output (I/O)interface(s) (not shown), or connector(s) (not shown), to functionallyattach to the conventional power grid. Power supply 265 also can includean energy conversion component(s) (not shown) such as a solar panel or athermoelectric device or material, which can be external or internal tothe device 202, in order to provide additional or alternative powerresources or autonomy to device 202.

FIGS. 3A-13C present various user interfaces that can be rendered by adevice (e.g., user equipment or customer premise equipment) that enablesvarious aspects of the subject innovation. In FIG. 3A, example userinterface (UI) 300 enables reporting of various network performanceincidents for a specific location. Indicia 302 conveys the specificlocation; e.g., “Current Location”. The device that renders UI 300 candetermine, or estimate, the “Current Location” based at least on globalnavigation satellite system (GNNS) data or time-of-flight (TOF)measurements, as described supra. In addition or in the alternative,soft-button 304 allows, when actuated, supplying the specific locationon a map; soft-button 304 can be actuated through various gestures(speech, touch, motion, etc.). In one or more embodiments, the map canbe rendered and positioned based at least in part on an address search.A group of indicia 306 represents a set of incidents that can bereported: Dropped Call, Failed Call Attempt, No Coverage, Data Failure,and Poor Voice Quality. It should be appreciated that other incidentscan be reported. Moreover, the network performance incidents representedby the group of indicia 306 are specific to incidents intelecommunication; incidents related to network performance for otherservices, such as recording of digital content, pay-per-view service,internet service, etc., can be represented by a disparate set ofindicia. In an aspect of the subject disclosure, a group of identifiersconveyed in indicia 308 enables characterization, or assessment, offrequency of the network performance incident: A selector block 309(e.g., a slider) can be utilized via a finger swipe or other gesture(voice, motion, etc.) to select one identifier from the group of “Once”,“Seldom”, “Often” “Always”. It should be noted that such identifiers areillustrative and other identifiers can be defined and exploited toassess frequency with which a network performance incident occurs.

Indicia 310 enables supplying additional information that furthercharacterizes the network performance incident. The additionalinformation can include comments related to the network performanceincident or its environment. In addition, in one or more embodiments,indicia 310 can allow rendition of information, e.g., views, related toreporting of network performance incidents. As an example, a view thatdiscloses all incidents reported by the device that renders example UI300 can be rendered in response to actuation of one or more soft-buttons(not shown) that is part of indicia 310; rendition of such view can beresponsive to configurable filter settings. As another example, a viewthat conveys operation details of a particular incident, current orhistorical, can be rendered in response to actuation of a soft-button(not shown) that is part of indicia 310.

Soft-button 312, when actuated, enables delivery of a report of anetwork performance incident. Support information for utilization of UI300 to report a network performance incident can be rendered through adisparate UI (not shown) in response to actuation of soft-button 314. Asan example, selection of incident indicia in group 306 (e.g., one of“Dropped Call”, “Failed Call Attempt”, “No Coverage”, “Data Failure”, or“Poor Voice Quality”, and actuation of soft-button 314 can result inrendition of information that explains the nature of the networkperformance incident represented by the incident indicia. In diagram300, selection of “Data Failure” soft-button is represented with anopen, slanted arrow. As another example, actuation of soft-button 314can render content that explains information that is available throughuser interface 300 or UI(s) derived there from. In addition, in certainscenarios, as part of the support information, the disparate UI (notshown) rendered in response to actuation of soft-button 314 can enabledelivery of data that identify a preferred Wi-Fi AP and nominate theWi-Fi AP to be part of a network of Wi-Fi APs, the data delivered to anetwork platform of a telecommunication carrier or service provider. Forexample, in such scenarios, the data can be delivered via email, wherethe disparate UI includes a link to a specific email address that whenselected causes the device (e.g., 202) that renders the disparate UI toexecute an email message delivery application; in device 202 suchapplication can be retained in application storage 291.

As discussed supra, the device that renders example UI 300 can perform adiagnostic cycle in response to a “Data failure” network performanceincident. In one example implementation, as presented in FIG. 3B, asubscriber can be prompted through a user interface 330 to perform thediagnostic cycle in response to reporting data failure through actuation(indicated with an open arrow) of “Data Failure” soft-button in FIG. 3A.The prompt can be accomplished through rendition of indicia 335 thatrequest input from the user device that renders example UI 300;rendition of such indicia can include darkening (indicated with a grey,shadowed area) of the various soft-buttons of example UI 300. Uponacceptance to perform the diagnostic cycle, which can be conveyedthrough actuation of a “Yes” soft button, the diagnostic cycle isperformed and a user interface 360, in FIG. 3C, is rendered to indicatethe diagnostic cycle is being conducted; indicia 365 in UI 360 conveysprogress of the diagnostic cycle. Data collected as part of thediagnostic cycle is delivered to the network operator. It should beappreciated that other user interfaces and related indicia can beemployed to prompt for acceptance of a diagnostic cycle and to conveyprogress of such diagnostic.

FIG. 4 presents an example UI 400 that illustrates a group 402 ofindicia that enables categorization or characterization, at least inpart, of a “Dropped Call” incident (selection highlighted with a thickline in group 306). Identifiers in the group 402 of indicia include“Indoor”, “Outdoor”, and “In_Transit”, and are selected via block 407(e.g., a slider block), which can be manipulated within the UI 400through a pressure-sensitive gesture (finger swipe) or other gestures.Manipulation includes lateral motion (indicated with arrows in thedrawing) across the various identifiers; manipulation can be accompaniedby aural indicia. While block 407 is illustrated as a semi-transparentrectangle, other representations can be employed such as wire-frameblock or a block that highlights an identifier when moved onto theidentifier. Such characterization is delivered as part of networkoperation data within a report (e.g., report 110) of the networkperformance incident.

FIG. 5 presents an example UI 500 that can enable interactive deliveryof feedback associated with a network performance incident. Whenactuated, a soft-button 510 renders a user interface through which achat-room communication can be established with a customer servicerepresentative of the network operator. In an aspect, when soft-button510 is actuated, the device (e.g., 202) that renders UI 500 can delivera request to initiate an interactive feedback exchange with a feedbacksystem (e.g., 140). In response to the request, the device can beprovisioned an interface to conduct an interactive session forexchanging information. The device renders the provisioned interface andexchanges data with the feedback system.

In FIG. 6, an example UI 600 conveys location of a network performanceincident in a map. The device (e.g., device 202) that renders example UI600 can retrieve the map from a server that is part of a networkplatform (e.g., 120) of the network operator or an external networkfunctionally coupled to the network platform (e.g., 120) and thatprovides location-based services. In an aspect, the device can retrieveexploit a collection component (e.g., 232) and a communication platform(e.g., 204). A block 602 of indicia allows determination of the incidentlocation through actuation of a “Current” soft-button; suchdetermination can be made in accordance with satellite-based data (e.g.,GNNS data) acquired by the device that renders example UI 600 or TOFmeasurements performed by the device, as described supra. In map 606,the estimated location of the network performance incident is presentedas a pin connected to a cross; other indicia can be employed as well. Inan aspect, the specific position of the pin and linked cross can bealtered through one or more gestures, such as pressure-sensitivegestures, which can include finger swipes or finger movement while incontact with a surface of a display in the device (e.g., 202) thatrenders the example UI 600. Such mode of providing a specific locationfor the network performance incident can be activated through selectionof “Map” in the block 610 of indicia, which enables various sources oflocation estimates. For example, selection of “Satellite” causes thedevice that renders example UI 600 to estimate a current location basedon GNNS data, whereas selection of “Hybrid” provides a location estimatebased on a combination of a selection on the map 606 and GNNS data. Inone or more embodiments, a “tracking mode” for the current location canbe enabled, wherein the pin and the cross connected thereto moves withina rendered map (e.g., 606) as the current location changes; thus, thelocation of the device that renders example UI 600 can be followed asthe device moves in real space. The rendered map (e.g., 606) positionsitself as the current location changes. In an aspect, the “trackingmode” can be activated if an “In Transit” selection is effected. Inanother aspect, the “tracking mode” can be activated if a dedicatedsoft-button (e.g., “Tracking Mode” button; not shown) in block 610 isactuated.

In addition, location(s) for which data that specifies a networkperformance incident is queued can be conveyed in a rendered map thatincludes location of the network performance incident; as an example,such location(s) are represented as grey-pins in map 606. Other indiciaalso can be employed to convey location(s) for a queued submission.Location(s) of previously reported network performance incidents alsocan be included in a rendered map that includes location of a networkperformance incident; as an example, in map 606, a pin with a concentriccircle can indicate location(s) of historical network performanceincident(s) and related report submission(s). In an aspect, in exampleUI 600, a “Clear” soft-button 608 can remove from the map one or morelocation(s) of previously reported network performance incidents. Otherindicia also can be employed to convey such location(s). Moreover, a setof open or semi-open confined-coverage access points (e.g., Wi-Fi APs,femtocell APs . . . ; represented with a circle with three arcs and adot) also can be displayed in the map 606. A confined-coverage accesspoint (AP) is generally deployed as part of a private or semi-privatedwelling; the confined-coverage AP provides wireless coverage to aconfined area owned or leased by the owner or lessee of theconfined-coverage AP, where the confined-area can encompass the privateor semi-private dwelling. Disclosure of location of a confined-coverageAP can guide a subscriber to areas of possible interest, e.g.,coffee-shop, health club, public library.

In one or more embodiments, such as example UI 620, a disclosureindicator 622 can be rendered on top, or otherwise attached to, of a pinlinked to a location to convey coordinates of the location (e.g.,latitude, longitude) and details of a report (e.g., type of report, dateof report . . . ) that has been submitted for the specific locationidentified by the pin. While illustrated for a current location pin inexample UI 620, the disclosure indicator 622, and pertinent coordinatesof location and details of a report can be rendered for any other pin(e.g., queued location, past submission location) that is rendered in UI620.

In additional or alternative embodiments, a soft-button (not shown) canbe included in example UI 600 to display, when the soft-button isactuated, cell tower (or macrocell base station) locations in a map(e.g., 606) and characterize such cell towers according to the radiotechnology (e.g., 2.5G, 3G, 3.5G, 4G . . . ) that the cell towers employto serve wireless service. In addition, further actuation of thesoft-button can render location(s) of planned cell tower constructionlocations. In an aspect, a collection component (e.g., 232) in thedevice (e.g., 202) that renders the cell tower locations, deployed orplanned, can receive from a display interface (e.g., 245) an indicationto query feedback system 140 and request available information ondeployment, current or planned, for macrocell base stations or any othertype of access point.

FIG. 7 presents an example UI 700 that can be rendered as landing pageafter an application (software or firmware) that allows to report anetwork performance incident is executed. A device that render exampleUM 700 can execute the application. As illustrated, example UI 700includes a set of soft-buttons arranged in six-pack format; whenactuated each soft-button provides results in rendition of additionaluser interface(s) that enable, at least in part, specific functionality.FIG. 8 conveys a specific example graphic representation of the set ofsoft-buttons; icons that represent soft-buttons 802-812 in diagram 800are spatially arranged in a one-to-one correspondence with blocks thatrepresent soft-buttons 702 through 712 in example UI 700. Namely,soft-button 802 corresponds to soft-button 702; soft-button 804corresponds to soft-button 704; soft-button 706 corresponds tosoft-button 806; soft-button 810 corresponds to soft-button 710;soft-button 812 corresponds to soft-button 712. In particular, thoughnot exclusively, example UI 700 includes a “Report” soft-button 702 thatenables supplying data that specifies a network performance incident.For example, actuation of soft-button 702 can render example userinterface such as 300, 400 or 500. In addition, example UI 700 includesa “Locate Wi-Fi” soft-button 704 that, when actuated, affordsidentifying Wi-Fi AP(s) or other confined-coverage APs in proximity tothe device that renders example UI 700. Example UI 700 also includes an“Optimize” soft-button 706 that, when actuated, enables optimization ofor otherwise adjustment to operation conditions of the device thatexecutes the application that allows to report the network performanceincident. Moreover, example UI 700 includes a “Network News” soft-button708 that, when actuated, enables access to feedback information (e.g.,feedback 150) from the network operator that provides the service forwhich the network performance incident is reported. In an aspect, thefeedback information includes Network Improvement alerts, which can bealerts directed to general improvements or to improvements specific toan area customized to a subscriber that utilizes the device that rendersexample UI 700. A number of network news or network alerts can berendered as part of soft-button 708, see e.g., soft-button 808 whichpresents an example realization of such number (“21”). Furthermore,example UI 700 includes a “Chat Room” soft-button 710 that, whenactuated, enables interactive exchange of information with a networkrepresentative as described supra. Still further, example UI 700includes a “Feedback” soft-button 712 that, when actuated, provides oneor more user interfaces to deliver supplemental information related witha reported incident or feedback linked therewith. In addition,soft-button 712 can enable, when actuated, delivery of other informationsuch as identification of a confined-area AP (e.g., Wi-Fi AP) andnomination of the confined-area AP to become a part of a network ofconfined-area APs administered by the network operator that provides theservice for which the network performance incident is reported.Moreover, when actuated, soft-button 712 allows the device that renderexample UI 700 to submit specific inquiries to the network operator andto receive related feedback or responses there from. It should bereadily appreciated that the set of soft-buttons is extensible and canbe modified to add soft-buttons that allow additional functionality. Forexample, a soft-button can be added to enable, at least in part,interactive or non-interactive exchange of information with peer-devices(or subscribers that own or lease such devices) as a result of actuatingthe soft-button.

FIG. 9 displays an example UI 900 that results from actuatingsoft-button “A” in a set of soft-buttons 904 that enables variousfunctionalities; the set of soft-buttons 904 is an additional oralternative representation of the set of soft-buttons rendered inexample UI 700. Such representation can be a carousel representation,which can be browsed through pressure-sensitive gestures (e.g., fingerswipes). As illustrated, soft-button “A” renders a user interface toreport a network performance incident. Likewise, FIG. 10 illustrates anexample UI 1000 that is rendered in response to actuation of soft-button“B” in the set of soft-buttons 904; such UI enables locating one or moreWi-Fi APs, or any confined-coverage AP, in proximity to the device thatexecutes the application that enables reporting of network performanceincident(s). In one or more embodiments, the application is either asoftware application or a firmware application stored in a memory in thedevice, and embodies an incident report component (e.g., 106), or one ormore component(s) therein. As illustrated, in example UI 1000, a “Scan”soft-button 1008 triggers measurement of various pilot signals that canidentify one or more Wi-Fi APs or confined-coverage APs. The measurementcan be performed by the device that renders the user interface; in oneor more embodiments, a scanner component (e.g., 225) in such device canscan the wireless environment of the device and obtain data on thevarious pilot signals and, based on the data, identify the set of Wi-FiAPs or other confined-coverage APs. In addition or in the alternative,actuation of “Scan” soft-button 1008 can result in collection from datastorage (e.g., a phonebook database) in the device or from a networknode (e.g., a database) of deployment data or availability data forWi-Fi APs near (e.g., at a distance of one or more typical coverageradius of a Wi-Fi AP) a current location of the device (e.g., R). Dataon availability of Wi-Fi APs, or any other confined-coverage APs, can beembodied in data that identify a Wi-Fi AP or any other confined-coverageAP and can be retained in the data storage within the device.

FIG. 11 presents an example UI 1100 that conveys a set of Wi-Fi APs, orany other type of confined-coverage APs, that are identified as a resultof scanning the wireless environment of the device or by retrieving(e.g., downloading) location data on Wi-Fi AP. As illustrated, openWi-Fi APs, Wi-Fi Protected Access (WPA) Wi-Fi APs, and WEP (WiredEquivalent Privacy) Wi-Fi APs can be identified. In certain embodiments,in addition to privacy or protection indicators for the Wi-Fi AP(s)other indicators that characterize the Wi-Fi AP can be rendered in auser interface or can be recorded in a memory (e.g., 285) in the devicethat renders example UI 1100 or other UI that conveys a list of Wi-FiAPs. For instance, the indicators that can be stored or rendered includereceived signal strength indicator (RSSI), service set identifier(SSID), basic service set identifier (BSSID), radio frequency (RF)Channel, medium access control (MAC) Address, or Protectionconfiguration (Open, WEP, or WPA presented in example UI 1100).Actuation of a soft-button in the set of indicia 1106 can render a UIthat allows connection to the Wi-Fi AP identified in the soft-button(e.g., “Location 2” Wi-Fi AP). If the device that renders the UI thatallows such connection receives an indication to connect to theidentified Wi-Fi AP, the device can execute a connection managerapplication (software or firmware) that can reside in the device, inmemory element 291 in device 202. If the device connects to theidentified Wi-Fi AP, the device can render an additional soft-buttonthat, when actuated, enables the device to record data that identifiesthe Wi-Fi AP within data storage (e.g., 293) in the device (202). In anaspect, the device that renders UI 1100 can automatically connect orattempt to connect to one or more Wi-Fi APs that are identified in datastorage, such as in an phonebook database, within such device.

Actuation of soft-button “E” renders example UI 1200 in FIG. 12. Variousaspects of device performance optimization can be enabled, asillustrated by the group of indicia 1206. Actuation of a soft-button inthe group of indicia 1206 can result in additional user interface(s)being rendered. Such UI(s) can allow exchange of data related tooperation of the device (e.g., 202), the data being specific toperformance that is intended to be optimized: For example, homeperformance, data performance, or battery. Actuation of “HomePerformance” soft-button 1208 or “Data Performance” soft-button 1210 canresult in data collection as described supra. For example, for “Homeperformance” a query-response UI can be rendered to convey a set ofquestions related to such performance: (1) “Can you make callseverywhere with good quality at home”; (2) “Do you have high-speedinternet at home?” “If yes, do you have Wi-Fi at home?”; and (3) “Do youhave a 3G Microcell at home?. Based on the collected responses, thedevice (e.g., 202) that renders example UI 1200 and the query-responseUI (not shown) can render additional user interface(s) to provideguidance (e.g., a “tip”) to improve network performance associated withthe reported incident. The guidance can be provided as a message, whichcan include a web-based link to details related to implementation of theguidance.

Actuation of “Battery” soft-button 1212 also can result in datacollection that probes operation condition of an existing battery withinthe device that render the example UI 1200. In addition, such actuationcan render at least one user interface that conveys battery optionsavailable for purchase from the network operator or one or more vendors;the at least one user interface can include a link to a web-basedinterface (e.g., webpage) in which the purchase can be conducted.Moreover, the at least one user interface can convey alternativeoperation configurations for the device that are directed to improvingbattery performance, such as executing a monitoring cycle that adjustsbacklighting intensity in the device's display(s) based on environmentin which the device operates.

Example user interface 1300 in FIG. 13A conveys indicia that enable, atleast in part, access to network operator feedback related to current orhistorical reports on network performance incident. A network operator(telecommunication carrier, service network provider, etc.) can providepart of the feedback based on a subscription and part of the feedbackbased on subscriber preference(s); in an aspect, a feedback system(e.g., 140) can generate and deliver the network operator feedback, asdescribed supra. Actuation of a soft-button in the group of indicia 1306can result in additional user interface(s) being rendered. As anexample, block of indicia 1306 includes a “National Network News”soft-button 1308 that, when actuated, causes the device that renders UI1300 to render information that can disclose planned networkdevelopments (e.g., deployment of 3G macrocell base station) or currentresponse to a class of network performance incidents (e.g., lack ofcoverage in a specific area). Information conveyed as a result ofactuation of “National Network News” soft-button 1308 can be disclosedas announcement(s); soft-button 1308 can present a number (K, a realnumber) of available announcements, or alerts, e.g., new announcements,announcements issued within a predetermined time interval, etc. ExampleUI 1330 in FIG. 13B represents the set of K announcements (“Message 1”,“Message 2”, “Message 3” . . . “Message K”) that can be rendered. Inaddition, example UI 1330 can include an “Unsubscribe” soft-button 1340that when actuated enables, in part, termination of a subscription tothe “National Network News” alert service. Likewise, block of indicia1306 can include a “Local Network News” soft-button 1310 that, whenactuated, can cause the device that renders UI 1300 to render feedbackinformation (e.g., announcements) for a specific area, which can beconfigurable and identified with a ZIP code or a geospatial entityobject code (geocode). Soft-button 1310 also can display a number (P, anatural number) of available announcements.

In addition, block of indicia 1306 can include a set of soft-buttonsthat conveys personalized feedback related to specific areas;personalization can be based at least on input received by the devicethat renders example UI 1300. Soft buttons 1312 and 1314 relate,respectively, to planned and complete “Personalized Reporting AreaNews”, where announcement(s) in response to one or more classes ofnetwork performance incidents for a selected area (e.g., a specific ZIPcode) are disclosed. Number of available announcements, or alerts, alsocan be rendered as part of soft-buttons 1312 and 1314; e.g., Qannouncements for planned response and R announcements for completeresponse, with Q and P integer numbers. Example UI 1360 in FIG. 13Crepresents the set of Q announcements (“Message 1”, “Message 2”,“Message 3” . . . “Message Q”) that can be rendered. In an aspect, eachrendered message can include a “Map” soft-button 1362 and a “Feedback”soft-button 1364. Actuation of soft-button 1362 causes, in part, thedevice (e.g., 202) that renders example UI 1360 to render a UI thatconveys a map with a location of the submission area related to themessage and indicia (e.g., a circle) surrounding the prospective, orplanned, network development. Actuation of soft-button 1364 can causethe device that renders the example UI 1360 to launch or execute anemail application (software or firmware) or any other electroniccommunication application retained in a memory (e.g., 291) within thedevice (e.g., 202).

A UI similar to example UI 1360 can be rendered in response to actuationof soft-button 1314. In an embodiment of the UI that is similar toexample UI 1360, feedback soft-button 1364 can be split in a pluralityof soft-buttons (e.g., three soft-buttons) with each soft buttoncharacterizing the subscriber response to the complete networkdevelopment (e.g., “Better Service”, “Same Service”, “Worse Service”).

In example UI 1300, soft-button 1316, when actuated, can result inrendering of feedback content for predetermined area(s) of interest,e.g., university campus, workplace area, tourism destination, area whererelatives live, or the like. In an aspect, content disclosed in responseto actuation of soft-button 1316 can include community features thatenable social interaction amongst subscribers that share an area ofinterest. For instance, subscribers that are interested in response of anetwork operator to issues that originate in a university campus canexchange messages in chat format, post messages in forum(s), or provideinformation in blog or micro-blog format.

FIG. 14 displays a block diagram of an example embodiment 1400 offeedback system 140 in accordance with aspects disclosed herein. Asindicated above, analysis component 144 receives data associated with anetwork performance incident from a set of devices 104 and analyzes thedata. The data can include contents of report 110 and associatedlocation (R) and time stamp (c) linked to the network performanceincident. In the illustrated example embodiment, analysis component 144includes an aggregation component 1406 that collects the data receivedfrom the set of devices 104 and also can acquire (receive, retrieve,etc.) network operation data from at least one functionality layer, suchas operation layer(s) 160 or external layer(s) 170. The aggregationcomponent 1406 can retain the results of the analysis in networkintelligence storage 1432, also referred to as network intelligence 1432in the subject specification and drawings. As described supra, dataassociated with a network performance incident or with operation of adevice (e.g., 202) that can report the network performance incident caninclude operation data of competing networks, network intelligence 1432can be recorded according to specific network, e.g., network 1, network2, . . . , network R, where R is natural number greater than or equal tounity; network intelligence (intel.) for network (net.) γ is retained innetwork k intelligence storage 1434 _(γ), also referred to as networkintel. 1434 _(γ), with γ=1, 2 . . . G, where G is a positive integer. Inaddition, based on analysis of data associated with a plurality ofnetwork performance incidents, analysis component 144 can producesubscriber intelligence that reveals various subscriber preferences,such as utilized device, contracted services, reporting behavior orreporting pattern, reporting areas, or the like. As an example,subscriber intelligence can include a subscriber profile that includessubscriber device(s) and one or more subscriber preferences. Analysiscomponent 144 can retain subscriber intelligence in memory 152 withinsubscriber intelligence storage 1440, also referred to as subscriberintelligence 1440. Subscriber intelligence 1440 also can includeinformation related to devices owned or leased by a customer andservice(s) subscribed by the customer. For example, subscriberintelligence 1440 can record a set of devices configured to reportnetwork performance incidents that a specific customer can operate andrelated feedback preferences, e.g., subscription to “Network News” andpersonalized areas for feedback (see, e.g., FIG. 13), and so on.

As part of the analysis, aggregation component 1406 can exploitassessment component 1412 to summarize, at least in part, the dataavailable (e.g., collected or acquired data) as a result of a pluralityof reports of network performance incidents. For example, aggregationcomponent 1406 can extract (I) data associated with reports of networkperformance incidents received from a plurality of subscribers in anarea proximate (e.g., within a predetermined radius or characteristicdistance) to location R at the time τ or at times within a predeterminedrange Δτ from τ; and (II) alarm status or key performance indicators fornetwork equipment that can affect service in the area proximate to R.Based at least on (I) and (II), and other customer-supplied informationrelated to a network performance incident or network performanceincident category, assessment component 1412 can provide an analysis ofnetwork operation condition. Such available data also can becategorized, for example, in accordance with type of network performanceissue or network problem. In one or more additional or alternativeembodiments of analysis component 144, assessment component 1412 canreside within aggregation component 1406.

Assessment component 1412 can operate on received or aggregated data togenerate at least one network performance metric, or network operationmetric, which is part of the network operation intelligence generated asa result of availability of the data reported by the set of devices 104.In an aspect, assessment component 1412 can compute one or more metricsassociated with reported data on network performance incidents from aset of devices (e.g., 104) and that specify, at least in part, aprobability that at least one device in the set of devices isexperiencing a network-related performance issue or a device-relatedperformance issue. In another aspect, from data collected from measuredpilot signals at a time of an incident or after an incident, assessmentcomponent 1412 can determine operational parameters of a set of one ormore competing network operators and retain such information inrespective one or more network intelligence storage, e.g., networkintelligence 1434 _(G), in memory element 1432. As an example,assessment component 1412 can compute at least one of a number of uniquesector identifiers per competing network operator or a number of uniquesector carriers per competing network operator. In yet another aspect,assessment component 1412 can review and classify information, or data,on existing plans for network development in specific areas for which aset of reports on network performance incidents and related data areavailable; such plans can include plans for improvements to existingdeployment(s) (e.g., optimization of deployment), new deployments ortechnology rollouts, new cell site builds, capacity augmentation (e.g.,acquisition of additional licenses to portions of electromagneticradiation spectrum), or the like. In still another aspect, based onaggregated data related to a plurality of network performance incidents,assessment component 1412 can generate, at least in part, a set ofnetwork interference matrices, wherein one or more matrices originatefrom interference measurements related to one or more competing networkoperators and the network operator that administers feedback system 140.Measurements of unique macrocell sector carriers performed by one ormore devices that report a network performance incident can allowcomposing a matrix of mutual interference between such carriers.

As part of generation of network performance metrics, assessmentcomponent 1412 can compare submitted tickets for service in a given areaand can normalize to the number of subscribers in the area that own orlease a device with a deployed (e.g., installed, tested, and active)incident report component (e.g., 106) to evaluate relative importance ofproblem areas. Such network performance metric can be employed forcapital allocation or investment prioritization. In addition, datacollected through network performance incident reports from customers ina specific area, with a Wi-Fi-enabled device but that do not utilize anavailable Wi-Fi AP in the specific area can be utilized to produce anddeliver (e.g., via direct mail, email, or other media) offers for Wi-Fiservice. Likewise, customer with a Wi-Fi enabled device with business orresidential internet service provided by the network operator thatprovide telecommunication service but do not have Wi-Fi service, alsocan be offered Wi-Fi service. In contrast to conventional marketing ofservices or products, service offerings described herein are based ondevice-driven customer-supplied data on network performance incidentsare highly customized and respond to an actual need, thus are morelikely to produce a commercial transaction (e.g., retention of Wi-Fiservice) than offerings provided through conventional mechanisms orsystems and based on typical data segmentation.

As part of analysis of data related to report of network performanceincidents, analysis component, via assessment component 1412, forexample, can produce clusters of reported incidents. As an example,network performance incidents within a predetermined time interval(e.g., a block of two rush hours, such as 6:30a-8:30a) and within apredetermined distance of each other can be part of a cluster. Clusterscan be categorized according to (A) clusters in an area with previouslyavailable information related to a network performance problem, e.g.,“known problem”, and (B) remainder clusters. As a result of suchcategorization, or filtering, provides clusters in areas with networkperformance problems for which network resources can be allocated toidentify a solution. As another example, network performance incidentscan be mapped to their closest base station (or cell tower) to formclusters of incidents that spatially coincide with deployed basestations. In an aspect, by mapping network performance incidents to abase station, analysis component 144 can trigger a service ticket (e.g.,a repair or maintenance ticket) for the base station based at least onnumber of reporting events, e.g., number of reports received from a setof unique reporting devices, for the base station. For instance, for thebase station, assessment component 1412 can monitor temporal evolutionof number of reports and, based on a set of rules, can identify a surgeor “spike” in number of reports and generate an alarm, which reportcomponent 1422 can provide to operation layer(s) 160 (not shown in FIG.14A), for example. Based at least on the alarm, one or more componentsin operation layer(s) 160 can generate a service ticket. Correlation ofidentified spikes and KPI for the base station, such as averagedropped-call percentage can be exploited to determine threshold(s) forsubscriber response to service degradation and thus effectively allocateresources to attain service performance compatible with subscriberresponse. Aggregation component 1406 can exploit intelligent component1420 to establish such thresholds, which can be retained as part ofnetwork intelligence 1432.

In example embodiment 1400, data mining component 1416 can enable, atleast in part, aggregation of acquired (received, retrieved, etc.) dataand the various operations of assessment component 1412. Data miningcomponent 1416 can extract data from data storage 1428 and can supplythe data to aggregation component 1406, which can process the data orrelay the data to assessment component 1412 for generation of networkintelligence as described above. Data mining component 1416 can exploit,at least in part, intelligent component 1420 in order to at leastextract spatial and temporal correlations between data or identify datapatterns or network performance patterns, which can includelocation-based network performance patterns. Intelligent component 1420can exploit various artificial intelligence (AI) methods.

Intelligent component 1420 also can exploit artificial intelligence (AI)methods to infer (e.g., reason and draw a conclusion based upon a set ofmetrics, arguments, or known outcomes in controlled scenarios) networkperformance incident(s) based at least on historical data of networkperformance incidents in a specific area or for a specific group ofsubscribers. In addition, intelligent component 1420 can exploit AImethods to optimize or to achieve a satisfactory utility trade-offbetween the cost of performing a network improvement directed toaddressing (e.g., solving) one or more categories of network problemsand the benefit of mitigating subscriber attrition as a result ofpresence of the one or more categories of network problems.

Artificial intelligence techniques typically apply advanced mathematicalalgorithms—e.g., decision trees, neural networks, regression analysis,principal component analysis (PCA) for feature and pattern extraction,cluster analysis, genetic algorithm, or reinforced learning—to a dataset. In particular, analysis component 144, or components therein, canemploy one of numerous methodologies for learning from data and thendrawing inferences from the models so constructed. Such methodologiescan be retained in memory 152 within algorithm storage. For example,Hidden Markov Models (HMMs) and related prototypical dependency modelscan be employed. General probabilistic graphical models, such asDempster-Shafer networks and Bayesian networks like those created bystructure search using a Bayesian model score or approximation can alsobe utilized. In addition, linear classifiers, such as support vectormachines (SVMs), non-linear classifiers like methods referred to as“neural network” methodologies, fuzzy logic methodologies can also beemployed. Moreover, game theoretic models (e.g., game trees, gamematrices, pure and mixed strategies, utility algorithms, Nashequilibria, evolutionary game theory, etc.) and other approaches thatperform data fusion, etc., can be exploited.

Analysis component 144, and one or more components therein, can utilizealgorithm(s) retained in memory element 1424 in addition to at least aportion of data stored in data cache 1436, to implement at least aportion of the various, previously described operations on received oraggregated data, e.g., mapping, assessment, data mining, classificationand segmentation, and so forth. It should be appreciated that data cache1436 also can be external to data storage 1428 or memory 244.Algorithm(s) retained in memory element 1424 also includes at least onemathematical algorithm for analysis of time series originated fromvarious reports of network performance incidents related to a specificarea, or market, a specific base station, and a unique set of reportingdevices (e.g., 104). For example, the at least one mathematicalalgorithm for analysis of time series can be defined or configured todetect (e.g., mathematically identify) a surge or spike in reporting ofnetwork performance incidents. When implemented, e.g., executed by aprocessor, such retained algorithm(s) can implement, at least in part,computation of statistics (e.g., averages, variances and standarddeviations, covariance matrices . . . ); generation of database views,e.g., specific subsets of data; extraction and representation of dataconnectivity; transformation of data for spectral analysis thereof basedupon Fourier transformation, wavelet transformation, . . . ; or thelike.

Algorithm(s) in algorithm storage 1424 also can include algorithms thatwhen implemented, e.g., executed by a processor, can afford to compressand extract data, or generate log records of data manipulation such asgeneration of network intelligence, creation of databases and new recordviews, or the like. Data compression can be accomplished at least inpart via lossless data compression, which can be employed for receiveddata that is deemed critical or strategic, or lossy compression for datathat is readily available.

Data stored in data cache 1436 can serve as a training set forgeneration of models of network operation, e.g., such as trafficdevelopment, marketplace exploitation, and so forth. Contents of datacache 1436 also can serve to conduct one or more integrity tests ofselected data, to ensure collected data is not corrupted or schedules ofplanned indoor scans are appropriate for collection of data for specifictypes of analysis.

In example embodiment 1400, findings of analysis of data acquired (e.g.,received or retrieved) through reports of network performance incidentscan be reported to various functional layers of a network operatornetwork. For example, reports of analyzed data or network intelligencecollected in network intelligence 1432 can be supplied to operationlayer(s) 160 or to a planning layer (not shown) to enable, at least inpart, network planning or network optimization (e.g., repairs). In anaspect, report component 1422 can generated reports of various aspectsof network intelligence retained in memory element 1432 and can supplythe reports to the various functional layers indicated supra. Reportcomponent 1422 can adjust format or content of a report base at least onthe intended recipient of the report. In certain embodiments, reportcomponent 1422 can request aggregation component 1406 to producespecific views (e.g., portions of data that satisfy a predeterminedcriterion) of available data. As an example, report component 1422 canviews of raw data (e.g., data that has not been analyzed) in accordancewith specific time of occurrence of an incident, specific location(s) orarea, specific category of incident, etc. Format of reported data caninclude charts, graphics, tables, or the like.

As an example of reports that enable, in part, network planning, FIG.14B illustrates a diagram 1450 of spatial distribution of two categoriesof network incidents in a predetermined area, which can be selected foranalysis; a first category of incidents is represented with uprightcrosses (+) and a second category is represented with slanted crosses(x). The predetermined area includes a first region 1452 associated witha first radio network controller and a second region 1456 associatedwith a second radio network controller; the first and second radiocontrollers can be part of access network(s) 114. In diagram 1450, athick line represents the boundary amongst the first region 1452 and thesecond region 1456. In addition, diagram 1450 also includes a set ofbase stations onto which a set of the incidents have mapped; such basestations are represented with rings. Moreover, a second set of basestations identified to have operational problems and are scheduled foror actively being repaired; hatched circles represent such basestations. It is noted that base stations in the second set are notidentified through device-driven reporting and associated analysisdescribed herein, but are identified via conventional mechanismsinstead. As illustrated, certain base stations in the first set and thesecond set are nearly overlapping in space; however, there are basestations in the first set that are not identified as problematic byconventional mechanisms. Moreover, there are base stations in the secondset that are in regions of low density of reported incidents, eventhough such base stations are being repaired or scheduled for repairs.Therefore, in an example scenario, based on data associated with reportsof network performance incidents and related analysis reported indiagram 1450, the network operator can allocate resources to repair basestations in group 1458 instead of base stations in group 1460.

Another feature of network intelligence provided through reports such asdiagram 1450 is that no-coverage areas can be unveiled and thus networkinvestment(s) can be directed to develop such areas; for example, area1462 indicates a region in which network performance incidents arereported and no base stations are deployed therein. Similarly, networkintelligence generated through analysis component 144 and conveyed inreports such as diagram 1400 can reveal regions with potential borderissues, such as area 1464.

FIG. 15 is a block diagram of an example network that can enable variousaspects of the subject innovation. Network platform 1508 can include oneor more functional elements, e.g., component(s), node(s), gatewaynode(s), interface(s), server(s), or platform(s) that enable bothpacket-switched (PS) (e.g., internet protocol (IP), frame relay,asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic(e.g., voice and data) and control generation for networkedcommunication, wireless or otherwise. In an aspect, network platform1508 embodies network platform 120 described herein. It should beappreciated that in cellular wireless technologies (e.g., 3GPP UMTS,HSPA, 3GPP LTE, 3GPP UMTS, 3GPP2 UMB), network platform 1508 embodies acore network. PS gateway node(s) 1518 can embody at least part the PSdomain. Functional element within the PS domain can enable exchange ofnotifications, indications, and directives in accordance with variousnetworked communication protocols indicated herein, including one ormore peer-to-peer transport protocol(s). With respect to CScommunication, network platform 1508 includes CS gateway node(s) 1515,which can interface CS traffic received from legacy networks liketelephony network(s) 1550 (e.g., public switched telephone network(PSTN), or public land mobile network (PLMN)) or a SS7 network 1580. CSgateway node(s) 1512 also can enable exchange of messagingcommunications in SMS protocol. In addition, CS gateway node(s) 1512 canauthorize and authenticate traffic (e.g., voice) arising from suchnetworks. Moreover, CS gateway node(s) 1512 can access mobility, orroaming, data generated through SS7 network 1560 in response to variousmobility events as described herein; for instance, the mobility data canbe stored in a VLR, which can reside in memory 1540. Furthermore, CSgateway node(s) 1512 can interface CS-based traffic or signaling with PSgateway node(s) 1518. As an example, in a 3GPP UMTS network, CS gatewaynode(s) 1512 can be embodied, at least in part, in gateway GPRS supportnode(s) (GGSN).

In the subject disclosure, in addition to receiving and processingCS-based traffic and signaling data, PS gateway node(s) 1518 canauthorize and authenticate PS-based data sessions (e.g., an incomingcall) with device(s) 1528 served through access network 1530 via link(s)1525 and link(s) 1527, which include wireline links (e.g., referencelinks) or wireless link(s) (e.g., line-of-sight (LOS) links). Device(s)1528 is a set of devices that includes wireless device(s), wirelinedevice(s), or a combination thereof. For example, device(s) 1528 caninclude a mobile device of a subscriber that exploits device-drivenreporting, related intelligence, and associated network feedback asdescribed herein, and a set of wireline devices that also can exploitdevice-driven reporting, related intelligence, and associated feedbackas described herein. Device(s) 1528 can embody the set of devices 104.

Access network(s) 1530 can include one or more components that enabletransmission of data and signaling, including related payload data,amongst device(s) 1528 and network platform 1508; access network(s) 1520can be part of access network(s) 152 and operate in substantially thesame or the same manner thereof. Access network(s) 1530 can include aradio access network (RAN), and associated component(s). The RANcomprises one or more macrocell base stations, and associated electroniccircuitry, and respective deployment site(s) of the one or moremacrocell base stations. In addition, the RAN includes theair-interface, which comprises a least one wireless radio link operatedin accordance with the base station(s) radio technology. It should benoted that the RAN comprises various coverage cells. For a wirelessdevice served by base station(s) (not shown), one or more networkcomponents that are part of a radio access network in access network1530 enable transmission of data and signaling. For wireline devices,one or more components that are part of a wireline network (e.g.,service network(s) 1590) enable the transmission of data and signaling.Link(s), represented with open arrows, operationally coupled to networkinterface(s) 1595 can deliver data and signaling to the wireline devicevia the one or more components of the wireline network, for examplerepresented by access network 1597, and related link(s) represented withopen arrows connecting the access network 1597 to device(s) 1528. Datasessions (e.g., an incoming call) can include traffic exchange withnetworks external to network platform 1510, such as wide area network(s)(WAN(s)) 1560 or service network(s) 1590; local area network(s) (LAN(s))1570 (e.g., enhanced 911) also can be interfaced with network platform1508 through PS gateway node(s) 1518. Network interface(s) 1595 enablethe traffic exchange; such interface(s) can include conventionalwireline or wireless links, or reference links specific to each of theexternal network(s) that interface with PS gateway node(s) 1518, orother portions of the PS domain in network platform 1508. In an aspect,PS gateway node(s) 1518 can generate packet data protocol (PDP) contextswhen a data session is established. To at least that end, in an aspect,PS gateway node(s) 1518 can include a tunnel interface (e.g., tunneltermination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which canfacilitate packetized communication with disparate wireless network(s),which can be part of access network(s) 1530 and can include Wi-Finetworks, femtocell network(s), macrocell network(s) and associatedradio access network(s) (RAN(s)) based on various radio technologygenerations, etc. It should be further appreciated that packetizedcommunication can include multiple flows of data that can be generatedthrough server(s) 1514, such as management server(s) (e.g., aprovisioning server, a mobility switching center (MSC)) or applicationserver(s), which, in certain embodiments, can implement at least a partof the functionality of server(s) 156. It is to be noted that in 3GPPUMTS network(s), PS gateway node(s) 1518 (e.g., GGSN) and tunnelinterface (e.g., TTG) comprise a packet data gateway (PDG).

In network environment 1500, network platform 1510 also includes servingnode(s) 1516 that conveys the various packetized flows of data streamsthat can be directed to device(s) 1528, and that are received through PSgateway node(s) 1518 from server(s) 1514. In turn, server(s) 1514 canreceive the communication(s), such as request for data intended toservice network(s) 1590, which can include an IP multimedia subsystem(IMS) core or other packet-based cores, from user equipment withindevice(s) 1528 or network elements. As an example, in a 3GPP UMTSnetwork, serving node(s) 1516 can be embodied in serving GPRS supportnode(s) (SGSN). As another example, in a 3GPP LTE network, servicenode(s) 1516 can be embodied in a Mobility Management Entity (MME).

Server(s) 1514 can operate in various layers of network platform 1508.For example, server(s) 1514 can operate as part of Operations SupportSystems (OSS), Business Support Systems (BSS), or network subsystemssuch as IMS core network. Server(s) 1514 can execute numerousapplications, which can include consumer-oriented application(s), suchas messaging services, location services, online gaming, wirelessbanking, or system-oriented applications, e.g., wireless devicemanagement, scheduling or queuing of network traffic, or the like. Suchapplication(s), either consumer-oriented or system-oriented, cangenerate sets of packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bynetwork platform 1510; in an aspect, the add-on features can include thecustomized communication processing described herein. Data streamsgenerated by server(s) 1514 can be conveyed to PS gateway node(s) 1518for authentication/authorization and initiation of a data session (e.g.,an incoming call), and to serving node(s) 1516 for communication todevice(s) 1528 thereafter.

Server(s) 1514 also can effect security (e.g., implement one or morefirewalls; see, e.g., 2530) of network platform 1508 to ensure network'soperation and data integrity in addition to authentication andauthorization procedures that CS gateway node(s) 1512 and PS gatewaynode(s) 1518 can enact. In addition, server(s) 1514 can implement timingprotocols (e.g., Network Time Protocol (NTP)) that supply timingframework(s) for various operation(s) of network platform 1508.Moreover, server(s) 1514 can provision services from externalnetwork(s), e.g., WAN(s) (wide area network(s)) 1560, LAN(s) (local areanetwork(s)) 1570, IMS core network, which can be part of servicenetwork(s) 1590, or Global Positioning System (GPS) network(s) (notshown). Server(s) 1514 can include one or more processors (not shown)configured to provide or that provide, in part, the functionality ofnetwork platform 1508. To that end, the one or more processors canexecute one or more sets of code instructions (not shown) stored inmemory 1540, for example.

In example network environment 1500, memory 1540 can store informationrelated to operation of network platform 1508. Information can includecontent(s), such as subscriber-generated content or from various othersources; subscriber account(s) and associated credential(s); pricingschemes, e.g., promotional rates, flat-rate programs, couponingcampaigns; and so forth. Memory 1540 also can store part of data relatedto implementation of device-driven reporting of network incidents,associated intelligence, and related network feedback and networkintelligence. In addition, memory 1540 can store information from atleast one of telephony network(s) 1550, WAN(s) 1560, LAN(s) 1570, SS7network 1580, or service network(s) 1590. While illustrated as a singleentity, memory 1540 can be distributed amongst one or more of thedescribed external networks, server(s) 1514, or other functionalelements of network platform 1510. Memory 1540 can be embodied at leastin part in a visitor location register (VLR), a home subscriber server(HSS), or storage available within a consolidated data repository thatcentralizes data (administrative data, operational data, etc.) for atleast network platform 120.

In view of the example systems described above, example methods that canbe implemented in accordance with the disclosed subject matter can bebetter appreciated with reference to flowcharts in FIGS. 16-21 and23-24, and call flow in FIG. 22. For purposes of simplicity ofexplanation, various methods disclosed herein are presented anddescribed as a series of acts; however, it is to be understood andappreciated that the claimed subject matter is not limited by the orderof acts, as some acts may occur in different order and/or concurrentlywith other acts from that shown and described herein. It is noted thatnot all illustrated acts may be required to implement a described methodin accordance with the subject specification. In addition, for example,one or more methods disclosed herein could alternatively be representedas a series of interrelated states or events, such as in a statediagram. Moreover, interaction diagram(s) or call flow(s) representseveral of the example methods disclosed herein in accordance with thedescribed subject matter; particularly in instances when disparateentities, or functional elements, enact disparate portions of one ormore of the several methods. Furthermore, two or more of the disclosedexample methods can be implemented in combination, to accomplish one ormore features or advantages described in the subject disclosure.

Methods disclosed throughout the subject specification and annexeddrawings are capable of being stored on an article of manufacture (e.g.,a removable volatile memory or non-volatile memory) to facilitatetransporting and transferring such methods to computers for execution,and thus implementation, by a processor, or for storage in a memory. Inan aspect, one or more processors, such as processor(s) that enact theone or more method described herein, can be employed to execute codeinstructions retained in a memory (volatile or non-volatile), or anycomputer- or machine-readable storage medium, to implement one or moreof the method described herein. Such code instructions provide acomputer-executable or machine-executable framework to enact the variousmethods described herein.

FIG. 16 displays a flowchart of an example method 1600 for reporting anetwork performance incident in accordance with aspects of the subjectdisclosure. In an aspect, a device, mobile or otherwise, can enact thesubject example method. In another aspect, one or more processorsconfigured to enable or that enable at least part of the functionalityof the device (UE, CPE, etc.) also can enact, at least in part, thesubject example method. At act 1610, an environment that enablesproviding information that specifies a network performance incident isrendered in a device, which is the device that implements, at least inpart, the subject example method. At act 1620, a location of the device(e.g., a position vector R; see FIG. 1) is established and at least thelocation is associated to the network performance incident. Positionvector allows determining an estimate of ground truth of the device andorientation of the device, such as heading. In addition, in certainembodiments, position vector can convey altitude, course, horizontalaccuracy or vertical accuracy. At act 1630, at least one time stamp isassigned to the network performance incident. In an aspect, the at leastone time stamp can be generated by the device. In another aspect, timinginformation received by the device, e.g., a GPS timing message can beutilized to determine the at least one time stamp. At act 1640, at leasta portion of the information that specifies the network performanceincident, the location of the device, and the time stamp are delivered.In one or more scenarios, various combination of information, location,and time stamp(s) also can be delivered; for instance, at least theportion of the information that specifies the network performanceincident and the location of the device can be delivered, but not thetime stamp assigned to the network performance incident.

At act 1650, feedback associated with the network performance incidentis received (see, e.g., FIG. 1), the feedback supplied by a networkoperator that provides communication service to the device through thenetwork in which the network performance occurs. In one or moreembodiments, the network operator can provide other service(s) inaddition to or instead of communication service; as an example, thedevice can be a digital video recorder (DVR) an the network operator canprovide entertainment via a pay-per-view subscription or contractedcable service.

FIG. 17 presents a flowchart of an example method 1700 for delivering atleast one of information that specifies a network performance incident,a location of a device that reports the network performance incident, ora time stamp assigned to the network performance incident, according toaspects of the subject disclosure. In one aspect, one or more acts ofthe subject example method can be part of act 1640 in example method1600. A device that enacts subject example method 1600 can enact thesubject example method 1700. At act 1710, it is determined if coverage,or service coverage, is available when reporting an incident. In one ormore embodiments, the incident is a network performance incident. In anaspect, “when reporting an incident” can refer to a time at which anenvironment that enables reporting the incident is rendered. In anotheraspect, the temporal reference “when reporting an incident” can refer toa period that commences at an instant prior to the incident and spans atime interval that includes the reporting of the incident.

A positive outcome to act 1710 directs the flow to act 1750, which isdescribed below. Conversely, a negative outcome of act 1710 directs theflow to act 1720, at which at least a portion of incident data (e.g.,time stamp, location of reporting device, content collected by thedevice . . . ) collected during reporting an incident is queued. Fordevices that implement the subject method and include GNNSfunctionality, a location estimate of the position of the device isgenerally available even though wireless service coverage can beunavailable when reporting the incident. For a device that implementsthe subject example method and lacks GNNS functionality and produceslocation estimate(s) based in part on time-of-flight measurements, alocation of the device when reporting an incident can be estimatedthrough historical location estimates, which can be retained, at leasttemporarily, in a memory within the device. At act 1730, at least theportion of incident data collected during reporting the incident isretained as part of historical incident data. In one or more embodiment,data storage 293 can retain the historical incident data.

At act 1740, it is determined if coverage is available after reportingthe incident. In an aspect of the subject disclosure, determiningavailability of coverage includes determining if coverage providedthrough one or more services alternative or additional to macro-cellularservice is available. For instance, the determining can include probingif femtocell service or Wi-Fi service is available; such probing can beaccomplished by scanning (e.g., collecting and decoding) pilot signalfor various services and assessing signal strength. A negative outcomeresults in re-enacting act 1740, whereas a positive outcome leads to act1750, at which it is probed if historical incident data is queued. Anegative outcome of act 1750 terminates the subject example method.Conversely, a positive outcome of act 1750, leads to act 1760, at whichthe historical incident data that is queued is delivered.

FIG. 18 presents a flowchart of an example method 1800 for supplyingend-user support content according to aspects of the subject disclosure.The device or the one or more processors that implement example methods1600 or 1700 also can implement the subject example method. At act 1810,it is determined if an incident report is provided. The determining canbe based on monitoring execution of at least one set of codeinstructions (e.g., a software application or a firmware application)that enable delivery of the incident report and related data. If thedetermining indicates that no incident report is provided, act 1810 isre-enacted. Conversely, if the determining establishes that an incidentreport is provided, then, at act 1820, an integrity probe cycle based atleast on the incident report is implemented. For example, for a “DataFailure” incident and associated report, a diagnosis loop, which can beembodied in one or more sets of code instructions retained in a memory(e.g., app. storage 291) can be executed by processor(s) 275.

At act 1830, operation support content is conveyed based at least on aportion of outcome of the integrity probe cycle. In an aspect, conveyingthe operation support content includes generating at least one messagethat includes a recommendation or an instruction associated with theincident report, and rendering the at least one message; the generatingand rendering effected by the device that implements the subject examplemethod. In one or more embodiment, the rendering includes displaying oneor more graphical user interfaces (GUIs) that disclose the at least onemessage. In another aspect, conveying the operation support contentincludes delivering at least one of a request and the portion of outcomeof the integrity probe to a backend service node, which can be part of abackend service system (e.g., 140), to generate and supply the operationsupport content.

In one or more embodiments, example method 1800 also can includereceiving information related to a network service that is available tothe device and that can improve performance of the device. In suchembodiment(s), a feedback system (e.g., 140) can generate theinformation based on historical data related to integrity probe cyclesfor the device, and can deliver the information to the device.

FIG. 19 is a flowchart of an example method 1900 for acquiringcompetitive data on network performance in accordance with aspectsdescribed herein. The device or the one or more processors thatimplement example methods 1600, 1700, or 1800 also can implement thesubject example method. At act it is determined if an incident report isprovided. This act is substantially the same or the same as act 1810. Ifthe determining indicates that no incident report is provided, act 1910is re-enacted, but if the determining establishes that an incidentreport is provided, then, at act 1920, a data harvest cycle thatcollects operational data of a telecommunication network based at leaston the incident report is implemented. The data harvest cycle can beembodied in one or more sets of code instructions stored in a memory(e.g., app. storage 291) or a computer-readable or machine-readablestorage medium; the one or more processors (e.g., 275) that implementthe subject example method 1900 can execute the one or more sets of codeinstructions. In an aspect, the implementing includes measuring (e.g.,detecting or decoding) pilot signal transmitted, or radiated, by a basestation or access point operated by an owned network or by a competingnetwork. At act 1930, at least a portion of the collected operationaldata is delivered. The delivering includes supplying such data to one ormore network nodes or one or more backend service nodes, which canprocess (aggregate, analyze, etc.) the operational data and relay theprocessed data to at least one functional layer (e.g., 160 or 170)operationally coupled to the one or more backend service nodes.

FIG. 20 is a flowchart of an example method 2000 for acquiringinformation, or data, on network performance in accordance with anaspect of the subject disclosure. In an aspect, at least one backendservice node (e.g., analysis component 144, feedback component 148,server(s) 156) can enact the subject example method. In another aspect,one or more processors can implement the subject example method, whereinthe one or more processors are configured to enable or enable, at leastin part, functionality of the backend service node. At act 2010,incident data is received from a set of one or more subscriber devices(e.g., device(s) 104). Incident data refers to data that characterizes anetwork performance incident, as described supra. At act 2020, theincident data is categorized, or classified, based at least on one ormore of historical incident data (e.g., reporting time interval),specific set of reporting devices, reporting area or market. At act2030, operational information associated with a category of the incidentdata is collected. The at least one backend service node that enacts thesubject example method can generate the operational information. In oneor more embodiments, feedback component 148 can retrieve or receive, orotherwise acquire, the operation information from at least one memorythat retains the operation information; the at least one memory can bepart of at least one of an operation layer (e.g., 160) and an externallayer (e.g., 170).

At act 2040, it is determined if operational information is unavailable.If operational information is unavailable, exception handling isimplemented at act 2050. In one example, exception handling includesissuing a service reference ticket to address the network performanceincident. In the alternative, if operational information is available,at least a portion of the operational information is conveyed at act2060. As discussed supra, the operational information can be conveyed asfeedback (e.g., 150) to at least one subscriber device that deliveredthe incident data.

FIG. 21 is a flowchart of an example method 2100 for acquiring feedbackon network operation and related performance incidents according toaspects described herein. The functional element(s) (backend servicenode, at least one processor, etc.) that implement example method 2000also can enact the subject example method 2100. At act 2110, a requestto deliver feedback data interactively is received. At act 2120, aninterface to receive feedback data interactively is provisioned inresponse to the request. Provisioning the interface can includeprovisioning a chat service or instant messaging service that enablesexchange of content amongst a device (mobile or otherwise) and a backendservice node or component(s) functionally coupled thereto. Provisioningthe interface to receive feedback data interactively also can includeenabling the interface to convey content in response to receivedfeedback data. At act 2130, the feedback data is collected interactivelythrough the interface.

FIG. 22 presents a call flow of an example method 2200 for establishinginteractive feedback delivery according to aspects of the subjectdisclosure. The subject example method complements example method 2200and illustrates at least one configuration of functional elements thatenable interactive delivery of feedback data. At act 2220, userequipment (UE) 2204 conveys a request for interactive feedback delivery.The request can be conveyed to gateway (GTY) node 2208 via an accessnetwork, such as a radio access network (RAN) (not shown in FIG. 22).Gateway (GTY) node 2208 receives the request and, at act 2224, relaysthe request to middleware component 2212, which transmits the request tofeedback system 2216 at act 2228. Feedback system 2216 provisions, atleast in part, an interface to receive interactive feedback at act 2232;the subject act or parts thereof can be implemented by middlewarecomponent 2212, GTY node 2208, and UE 2204, which can exchange variousmessages, which can be grouped in groups 2236, 2240, and 2244, to enablethe provisioning. For instance, messages associated with authenticationof UE 2204 can be exchanged amongst UE 2204 and at least one serverwithin feedback system 2216, wherein such messages are relayed by GTYnode 2208 and middleware component 2212. As another example, theprovisioning act 2232 can include establishing a secure tunnel forcontent delivery in accordance with one or more secure protocols, suchas SCP, SSH, SFTP, or the like.

In an aspect, the provisioning act 2232 includes initiating a chatsession and rendering a user interface to in UE 2204 to receive inputdata and convey input; the input data can be received from an end-useror from at least one component (e.g., feedback component 148) that ispart of feedback system 2216. Input data received by the UE 2204 fromthe at least one component can be generated within a customer servicelayer, which can be part of external layer(s) 170, and supplied to theat least one component for delivery to UE 2204. In one or moreembodiments, device 202 can embody UE 2204 and feedback system 140 canembody feedback system 2216.

FIG. 23 is a flowchart of an example method 2300 for producing networkintelligence based at least on data received through reporting of one ormore network performance incidents according to aspects of the subjectdisclosure. The produced network intelligence can be exploited at leastfor network planning and investment prioritization, and related networkplanning and optimization (see, e.g., FIG. 14B and associateddescription). At act 2310, network operation data from a device isreceived in response to a performance incident report. At act 2320,network operation intelligence based at least on the network operationdata is generated. At act 2330, the received network operation data andthe generated network operation intelligence is retained. The networkoperation intelligence can be retained for further processing and fordeveloping investment allocation plans, and for optimizing the networkfor which operation data is received. As an example, if the networkintelligence reveals that a substantive number of subscribers (ascompared to a predetermined threshold, for example) in an area havereported “no coverage”, the network operator that exploits the networkoperation intelligence can invest resources to enhance service providedto the subscribers in the area. At act 2340, at least one of a portionof the received network operation data or a portion of the generatednetwork operation intelligence are delivered.

FIG. 24 is a flowchart of an example method 2400 for supplying datarelated to a specific network service associated with a networkperformance reporting system according to aspects described herein. Inan aspect, the subject example method 2400 can be implemented by acomponent in feedback system 140, or one or more components therein(e.g., feedback component 148). In another aspect, the subject examplemethod 2400 can be implemented, at least in part, by a server (e.g.,server(s) 156) that provide or are configured to provide thefunctionality of the feedback system 140 as described supra. At act2410, a request for data for a specific service that is part of adevice-driven network performance reporting system is received from arequester component. In an embodiment, the requestor component is acomponent (e.g., collection component 232) in a device that can reportnetwork performance incidents, such as device 202. In such embodiment,the request can be related to one or more of (i) subscription to anetwork feedback service or termination of subscription to the networkfeedback service, (ii) access to specific network alerts; (iii) accessto a location-based service that can provide a ground truth estimate forthe device; (iv) access to map(s) and information related to networkdevelopment plans; or the like. In another embodiment, the requestorcomponent can be a planning tool component that is part of operationlayer(s) 160.

At act 2420, the data is acquired based on the specific network service.As an example, if the request is a query for network news, the feedbacksystem component (e.g., feedback component 148) that implements thesubject example method, can acquire the data from an operation layer, ora network node therein, such as a memory or memory element. In thealternative or in addition, the feedback system component (e.g.,feedback component 148) can acquire the data from a memory that is partof the feedback system (e.g., 140). As another example, if the requestrelates to access to network intelligence produced in the feedbacksystem, the feedback system component can access memory 152 and acquirethe data.

At act 2430, the data is delivered to the requestor component. In one ormore embodiments, a report component in feedback component 148 canconvey the data. Delivering the data includes conveying a data message,with at least a portion of the data as payload, or conveying a SMScommunication or MMS communication, wherein either of suchcommunications can transport the data as payload.

FIG. 25 illustrates a block diagram of an example system 2500 thatenables various aspects described herein. The example system 2500includes a set of one or more device(s) 2504 and a logical grouping ofvarious tiers that enable disparate functionality associated withdevice-driven intelligence and related feedback, and generation ofnetwork intelligence. The set of one or more device(s) 2504 can embodythe set of devices 104; in an aspect, at least one device in the set ofone or more device(s) 2504 includes an incident report component (e.g.,106). A tier can include component(s), electronic circuitry, server(s),memory(ies), or any combination thereof. Various tiers can be connectedthrough wired or wireless links, reference links, various busarchitectures, or any combination thereof. Client presentation tier 2510enables communication with at least one device in the set of one or moredevice(s) 2504, and can include access network(s) 114. In addition,client presentation tier 2510 manages connectivity of the at least onedevice with multichannel access gateway 2520.

Mutichannel access gateway 2520 comprises client access tier 2524 andbusiness service access tier 2528 In an aspect, client access tier 2524can authenticate a client application (e.g., incident report componentthat is embodied in a set of code instructions retained in a memory andexecuted by a processor in the at least one device) and can authorizethe client application. In another aspect, client access tier 2524 canimplement data validation, and can manage format of data exchangedbetween client presentation tier 2510 and business services tier 2530.In certain embodiments, gateway node(s) (e.g., 124) that can be part ofa network platform (e.g., 120) can reside in client access tier 2524.

Business service access tier 2528 can implement service registrationwith external layer(s) (e.g., 170) and session management for a clientapplication and a related service (e.g., a back-end application). Inaddition, business service access tier 2528 can implement datatransformation to ensure suitable delivery to a device in the set of oneor more device(s) 2504; data that is transformed can be data exchangedbetween the device and a related client application and a backendservice. In certain embodiment, gateway node(s) (e.g., 124) that can bepart of a network platform (e.g., 120) can reside in business serviceaccess tier 2528.

Business services tier 2530 can administer back-end services. Forexample, business service tier 2530 can enable back-end service(s);authorize and authenticate a service consumer; and apply businessrule(s) and logic. In an aspect, feedback system 140 can be deployed(e.g., installed, tested, and utilized) as part of business servicestier 2530. In another aspect, at least a portion of operation layer(s)160 can be deployed as part of business services tier 2530. Data that isreceived, generated, or otherwise available at business services tier2530 can be retained in business data tier 2540. For example, networkintelligence produced as a result of analysis of data associated with aplurality of reports of network performance incidents can be stored inmemory elements (databases, tables, registers, etc.) that are deployedas part of business data tier 2540.

Security tier 2550 enables, at least in part, various security featuresthat can be implemented in one or more tiers, such as client access tier2524, business service access tier 2528, or business services tier 2530.Security tier 2550 also can implement encryption/decryption, managementof tokens, security socket layer (SSL) protocol, and so forth.Credentials or any information relevant to implementation of securityfeatures can be retained in memory element(s) within business data tier2540.

Service management tier 2560 can enable data caching, loggingprocedures, performance management, and fault management. In an aspect,as part of performance management, service management tier 2560 canenable load management (e.g., load balancing) in the client access tier2524 and business service access tier 2528. In another aspect, servicemanagement tier 2560 can implement application server clustering inbusiness service access tier 2528.

FIG. 26 illustrates a block diagram of an example system 2600 thatenables various aspects described herein. The subject example system2600 embodies, in part, feedback system 140. The parts of example system2600 that embody the feedback system 140 include load balancer 2610,proxy server(s) 2620, firewall 2630, application server(s) 2640, webserver(s) 2650, and security server(s) 2660. Analysis component 144 andfeedback component 148 can be part of application server(s) 2640, whichcan embody server(s) 156. Reports supplied to network platform 120 froma device within the set of one or more device(s) 2604 can be received atthe network platform through a radio access network (RAN) that is partof access network(s) 114 and directed to load balancer 2610 via anaccess network (e.g., the internet) that is part of access network(s)114. The device includes an incident report component (e.g., 106). Loadbalancer can determine a proxy server within the set of proxy servers2620 to route the report (e.g., 110) and related data through firewall2630 to application server(s) 2640.

Prior to receiving a report, credential of the device that utilizes(e.g., executes) the incident report component 106 is validated througha CSP XML (extensible markup language) API (application programminginterface) via security server(s) 2660. The security sever(s) 2660 canbe embodied in cryptographic service provider (CSP) server(s). Thedevice (e.g., device 202) that is validated can exploit keychainsoftware for persistence of username and password, session ID,application identity (ID), application passcode, or other securitycredentials; in an aspect, such credentials can be delivered in HTTPSHeaders as part of delivery of data (reports, supplemental data, etc.),received from the device. In addition or in the alternative, webserver(s) 2650 can perform CSR lookup prior to implementation of variousfeedback system 140 methods, as described supra (e.g., FIG. 20-23).

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD) . . . ), smart cards, and flashmemory devices (e.g., card, stick, key drive . . . ).

It should be appreciated that while various aspects, features, oradvantages described herein have been illustrated with reference toWi-Fi access point(s) and associated Wi-Fi coverage, such aspects andfeatures also can be exploited for most any type, or any type, ofconfined-coverage access point(s) (CCAPs) that provide wireless coveragethrough substantially any, or any, disparate telecommunicationtechnologies, such as for example femtocell telecommunication orpicocell telecommunication. Additionally, aspects, features, oradvantages of the subject disclosure can be exploited in substantiallyany wireless telecommunication technology, or radio technology; forexample, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX),Enhanced General Packet Radio Service (Enhanced GPRS), 3GPP LTE, 3GPP2UMB, 3GPP UMTS, HSPA, HSDPA, HSUPA, or LTE Advanced. Moreover,substantially all aspects of the subject innovation can include legacytelecommunication technologies.

What has been described above includes examples of systems and methodsthat provide advantages of the subject innovation. It is, of course, notpossible to describe every conceivable combination of components ormethodologies for purposes of describing the subject innovation, but oneof ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,”“incorporates,” “has,” “possesses,” their variations, and the like areemployed in the detailed description, claims, appendices and drawingssuch terms are intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

1. A method, comprising: rendering in a device an environment forproviding information that specifies a network performance incident;delivering at least a portion of the information that characterizes thenetwork performance incident; and receiving at the device feedback dataassociated with the network performance incident in response to thedelivering act, wherein the feedback data is supplied by a network nodeadministered by a network operator that provides a communication serviceto the device.
 2. The method of claim 1, the group of acts furthercomprising: establishing a location of the device and associating thelocation to the network performance incident, wherein the networkperformance incident is at least one of (i) a dropped call, (ii) afailed call attempt, (iii) lack of coverage, (iv) data failure, or (v)non-satisfactory voice quality.
 3. The method of claim 2, the group ofacts further comprising: assigning at least one time stamp to thenetwork performance incident.
 4. The method of claim 2, wherein theestablishing act includes receiving an indication that defines thelocation.
 5. The method of claim 2, wherein the establishing actincludes receiving global navigation satellite system (GNNS) data anddetermining the location based at least on the GNNS data.
 6. The methodof claim 2, the establishing act comprising: generating a locationestimate of the location of the device based at least on atime-of-flight assessment which includes at least one of determining atiming advance (TA), generating a round trip time (RTT), a time ofarrival (TOA), or determining a time difference of arrival (TDOA); oracquiring the location of the device from an external system thatprovides network location based services.
 7. The method of claim 1, thegroup of acts further comprising: in response to the delivering act,collecting diagnostic data based at least on the information thatspecifies the network performance incident.
 8. The method of claim 7,the group of acts further comprising: conveying operation supportcontent based at least on a portion of the outcome of the integrityprobe cycle.
 9. The method of claim 1, the group of acts furthercomprising: in response to the delivering act, collecting operationaldata of a telecommunication network based at least on the informationthat specifies the network performance incident.
 10. The method of claim9, wherein the collecting act includes probing operational data of oneor more of (i) at least one competitor network or (ii) an owned network.11. The method of claim 9, further comprising: delivering at least aportion of the collected operational data.
 12. A device, comprising: adisplay interface that renders an environment to acquire data thatspecifies a network performance incident; an incident report componentthat receives the data, the data comprising a category of the networkperformance incident, a location estimate for the network performanceincident, and a time stamp for the network performance incident; and acommunication platform that delivers the data to a network node thatprovides a network service to the device.
 13. The device of claim 12,wherein the data further comprises information that specifies at leastone of operation condition of the device or an operation environment ofthe device at a time the network performance incident occurred.
 14. Thedevice of claim 12, wherein the incident report component receivesfeedback data from the network node in response to delivery of the data,the feedback data conveys a response to the network performanceincident.
 15. The device of claim 14, wherein the incident reportcomponent includes a collection component that queues the data if thenetwork service is unavailable, the collection component delivers thedata when the network service is restored.
 16. The device of claim 12,wherein the incident report component includes a location component thatproduces the location estimate or acquires the location estimate from anetwork node that provides network location based services.
 17. Thedevice of claim 12, further comprising a scanner component that performsan integrity cycle and, based on the outcome of the integrity cycle,wherein the scanner component: issues a recommendation of a mode ofoperation for the device; or switches a mode of operation of the device.18. The device of claim 17, wherein the integrity cycle is a diagnosticcycle and the recommendation includes an indication to switch from afirst radio technology to a second radio technology, the scannercomponent performs the diagnostic cycle in response to a specificnetwork performance incident.
 19. The device of claim 17, wherein thescanner component detects pilot signals in the vicinity of the deviceand, based at least on the pilot signals, the scanner componentidentifies a set of confined-coverage access points (APs), wherein aconfined-coverage AP in the set of confined-coverage APs serves aconfined area that is leased or owned by the owner or lessee of theconfined-coverage AP.
 20. A computer-readable storage medium having codeinstructions stored thereon that, when executed by at least a processor,the code instructions perform at least the following acts: rendering anenvironment for providing information that specifies a networkperformance incident; delivering at least a portion of the informationthat characterizes the network performance incident; and receivingfeedback data associated with the network performance incident inresponse to the delivering act, wherein the feedback data is supplied bya network node administered by a network operator that provides anetwork service to the device.